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

Alias hostname cannot be resolved

Scheduled Pinned Locked Moved Firewalling
3 Posts 2 Posters 1.2k 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.
  • M
    mikepell
    last edited by Feb 28, 2013, 12:36 PM

    2.0.2-RELEASE

    I have created numerous aliases.  While doing so, I made a typo.  I have an alias named "alias1" containing hosts.  There was an ip address with a typo "12.3456.78" which should have been "12.34.56.78".  There is a recurring error in the system log "host_dns: failed looking up "12.3456.78"".  My understanding is that if an alias is not able to be resolved, any rules containing that alias are not applied.

    I have done the following, none of which have resolved the host_dns error being logged:

    -corrected the typo and applied
    -toggled each rule containing the alias and applied
    -renamed "alias1" to "alias_1" and applied

    I have downloaded the config file and verified that there is no occurrence of the typo.  Every 5 minutes, I still see the host_dns error with the typo in the log.  A am at a loss as to how I can fix this.

    1 Reply Last reply Reply Quote 0
    • D
      DerBachmannRocker
      last edited by Feb 28, 2013, 2:24 PM

      My guess is the system uses some kind of cache and resolves the hostname only at time X. I'm stating the obvious here, but just in case: did you try to reboot your firewall?

      1 Reply Last reply Reply Quote 0
      • M
        mikepell
        last edited by Feb 28, 2013, 2:52 PM Feb 28, 2013, 2:39 PM

        Rebooting was the first thing I thought of, but the last thing I want to do.

        I just replicated the issue in a test environment, and rebooting certainly "fixed" it.  I will have to schedule a reboot of the production box at a time when it will have minimal impact.

        Unfortunately, does this imply that a reboot is required to ensure changes to aliases are fully applied?

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