• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Snort could not resolve host

Scheduled Pinned Locked Moved IDS/IPS
3 Posts 2 Posters 572 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P
    phantonuser
    last edited by Mar 13, 2019, 7:16 PM

    Hello All,

    Snort is not updating the rules.

    Here is the error message.

    Starting rules update... Time: 2019-03-13 15:53:04
    Downloading Snort Subscriber rules md5 file snortrules-snapshot-29120.tar.gz.md5...
    Snort Subscriber rules md5 download failed.
    Server returned error code 0.
    Server error message was: Could not resolve host: www.snort.org
    Snort Subscriber rules will not be updated.
    Downloading Snort GPLv2 Community Rules md5 file community-rules.tar.gz.md5...
    Snort GPLv2 Community Rules md5 download failed.
    Server returned error code 0.
    Server error message was: Could not resolve host: www.snort.org
    Snort GPLv2 Community Rules will not be updated.
    Downloading Emerging Threats Open rules md5 file emerging.rules.tar.gz.md5...
    Emerging Threats Open rules md5 download failed.
    Server returned error code 0.
    Server error message was: Could not resolve host: rules.emergingthreats.net
    Emerging Threats Open rules will not be updated.
    The Rules update has finished. Time: 2019-03-13 15:56:04

    I appreciate any help.

    Thank you.

    1 Reply Last reply Reply Quote 0
    • B
      bmeeks
      last edited by Mar 15, 2019, 2:24 PM

      Did you try to force the rules update again manually? This is likely a temporary error on your end with DNS name resolution. My Snort rules updated just fine on March 13th.

      If it is still failing to update for you, then you need to investigate the DNS settings on your firewall.

      P 1 Reply Last reply May 27, 2019, 4:28 AM Reply Quote 1
      • P
        phantonuser @bmeeks
        last edited by May 27, 2019, 4:28 AM

        @bmeeks It was a DNS issue. After I configured DNS Resolver properly it began to work again.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received