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

    DNS resolver not resolvering hosts in alias

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

      I have the default route over VPN and i created an alias for machines to go direct via wan using an alias.
      e.g. netgate.com is one.

      The general settings has only 127.0.0.1 as the dns server
      NAT forward directs DNS to local interfaces for each one
      Pass rule for !firewall for DNS on each interface
      Block rule * for DNS on each interface

      client dns resolution works - or i wouldn't be writing now.

      in the resolver log, i keep getting - the below errors which are hosts defined in the alias for vpn_bypass
      filterdns failed to resolve host www.changiairport.com will retry later again.
      filterdns failed to resolve host protonmail.com will retry later again.

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by Gertjan

        Hi,

        [2.4.5-RELEASE][admin@pfsense.mynetwork.net]/root: host www.changiairport.com
        www.changiairport.com has address 52.220.76.76
        www.changiairport.com has address 18.140.162.186
        [2.4.5-RELEASE][admin@pfsense.pfsensemynetwork.net]/root: host protonmail.com
        protonmail.com has address 185.70.41.35
        protonmail.com mail is handled by 5 mail.protonmail.ch.
        protonmail.com mail is handled by 10 mailsec.protonmail.ch.
        

        You have DNS issues.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        4 1 Reply Last reply Reply Quote 0
        • 4
          4o4rh @Gertjan
          last edited by

          @Gertjan actually, i think i am suffering from this issue
          https://redmine.pfsense.org/issues/5413
          I will try to disable the DHCP lease registration and see if that helps.

          1 Reply Last reply Reply Quote 0
          • 4
            4o4rh
            last edited by

            I can confirm, i did have the same problem as in the bug report. disabling the DHCP lease registration worked for me as a workaround too.

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