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

    Filterdns: host_dns: failed looking up

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 6.3k 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.
    • C
      cbrunet
      last edited by

      What does this error means? I have full of them into logs, but I cannot figure out where it comes from.

      filterdns: host_dns: failed looking up "mailshell.net": hostname nor servname provided, or not known

      Charles.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        It means you are using that hostname in an alias or IPsec endpoint, and it cannot be properly resolved by your DNS server.

        Indeed that hostname does not have a valid record. It comes back empty.

        $ ping mailshell.net
        ping: cannot resolve mailshell.net: No address associated with name
        $ host mailshell.net
        $
        $ host -t mx mailshell.net       
        mailshell.net has no MX record
        

        So wherever you have that hostname, it isn't valid to use, since it must return an IP address to be used in firewall rules.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • C
          cbrunet
          last edited by

          Yes, I understand that. But what I cannot figure out is where those hostnames are registred in pfSense. I though it was in Captive Portal Allowed Hostnames, but I removed all invalid hostnames, and I still get those errors in the logs.

          Charles.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            It can be anywhere a hostname is allowed: firewall aliases, IPsec endpoints, captive portal allowed hostnames, etc.

            It might be easier to download a copy of the config.xml (From Diagnostics > Command) and then search through the file to see where it is.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.