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

    DNS Resolver

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    186 Posts 44 Posters 135.5k 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.
    • W
      wagonza
      last edited by

      @feld:

      Settings aren't sticking

      Can't resolve anything unless I disable forwarders

      Disabling forwarders breaks my ability to forward domains to certain servers

      Still the case in latest snap?

      Follow me on twitter http://twitter.com/wagonza
      http://www.thepackethub.co.za

      1 Reply Last reply Reply Quote 0
      • W
        wagonza
        last edited by

        @stompro:

        Can someone point me to the reasoning/discussion on why dnsmasq is being replaced?  I've always been happy with it.

        Well Unbound is now in base of FreeBSD 10.X so it makes it (pfSense) easier to maintain.

        Follow me on twitter http://twitter.com/wagonza
        http://www.thepackethub.co.za

        1 Reply Last reply Reply Quote 0
        • Raul RamosR
          Raul Ramos
          last edited by

          Hi

          2.2-ALPHA (amd64)
          built on Tue Jul 22 01:18:23 CDT 2014 (Full)

          • Settings are sticking, i don't test if are working or not.

          • Can delete networks when edit one access list (what access list is for? been there or not is the same thing, some check box to only allow allowed lists? or i need one to reject all networks first?).

          • Hosts seems OK.

          • Host Override works but aliases don't.

          • Only the first domain works on Host Override. If i configure multiple domains to a IP or multiple IPs only the first one seems to work.

          • Not tested yet domain override. I'll.

          Edit: My DNS clients take the DNS from General Setup -> DNS Servers (the first-one) and not the pfsense IP. My DNS Servers in system information and in interface are 127.0.0.1 and those in General Setup -> DNS Servers (should have my ISP to from my pppoe connection).

          Edit2: For some reason My Ubuntu server 14.04 in VirtualBox doesn't resolve any host or domain said:

          "xxxxx@BoxHost:/etc$ nslookup
          > pfsense
          ;; reply from unexpected source: 10.0.30.1#53, expected 10.0.0.1#53"
          

          10.0.0.1 is Lan IP (vlan) and 10.0.30.1 is another Vlan where My ubuntu server network are.

          pfSense:
          ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
          Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
          NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            @wagonza:

            @stompro:

            Can someone point me to the reasoning/discussion on why dnsmasq is being replaced?  I've always been happy with it.

            Well Unbound is now in base of FreeBSD 10.X so it makes it (pfSense) easier to maintain.

            and dnsmasq has some really poor failure modes.

            and … dense support is completely missing for dnsmasq

            1 Reply Last reply Reply Quote 0
            • M
              m3usv0x
              last edited by

              @mais_um:

              Hi

              2.2-ALPHA (amd64)
              built on Tue Jul 22 01:18:23 CDT 2014 (Full)

              • Settings are sticking, i don't test if are working or not.

              • Can delete networks when edit one access list (what access list is for? been there or not is the same thing, some check box to only allow allowed lists? or i need one to reject all networks first?).

              • Hosts seems OK.

              • Host Override works but aliases don't.

              • Only the first domain works on Host Override. If i configure multiple domains to a IP or multiple IPs only the first one seems to work.

              • Not tested yet domain override. I'll.

              Edit: My DNS clients take the DNS from General Setup -> DNS Servers (the first-one) and not the pfsense IP. My DNS Servers in system information and in interface are 127.0.0.1 and those in General Setup -> DNS Servers (should have my ISP to from my pppoe connection).

              Edit2: For some reason My Ubuntu server 14.04 in VirtualBox doesn't resolve any host or domain said:

              "xxxxx@BoxHost:/etc$ nslookup
              > pfsense
              ;; reply from unexpected source: 10.0.30.1#53, expected 10.0.0.1#53"
              

              10.0.0.1 is Lan IP (vlan) and 10.0.30.1 is another Vlan where My ubuntu server network are.

              I can second the above in bold. I cannot get pfSense to serve itself as DNS, instead it pushes ISP DNS.
              Am I missing something?

              1 Reply Last reply Reply Quote 0
              • MikeV7896M
                MikeV7896
                last edited by

                @m3usv0x:

                I can second the above in bold. I cannot get pfSense to serve itself as DNS, instead it pushes ISP DNS.
                Am I missing something?

                I'll third this… pfSense is not providing the router's IP address as the DNS server for clients to use when DNS Resolver is enabled. All works correctly when DNS Forwarder is used instead.

                The S in IOT stands for Security

                1 Reply Last reply Reply Quote 0
                • G
                  grandrivers
                  last edited by

                  yes i noticed this also in 2.1.4 when doing some troubleshooting

                  pfsense plus 25.03 super micro A1SRM-2558F
                  C2558 32gig ECC  60gig SSD

                  1 Reply Last reply Reply Quote 0
                  • F
                    Fegu
                    last edited by

                    Just to bump this: pfSense is not providing the router's IP address as the DNS server for clients to use when DNS Resolver is enabled. All works correctly when DNS Forwarder is used instead.

                    I tried with and without Enable Forwarding Mode. I also made sure that the override box in General Settings is off.

                    Also, slightly related, the dropdown options on the advanced settings page are all at the first option as default, while the legends/help texts underneath claim that default values are something else.

                    1 Reply Last reply Reply Quote 0
                    • MikeV7896M
                      MikeV7896
                      last edited by

                      Another bump, but also something different…

                      I recently changed back from ISP DHCPv6+PD to my HE tunnel, and in doing so I re-enabled the DHCPv6 server in pfSense. Anyway... after those changes were made, I disabled DNS Forwarder and enabled DNS Resolver. Pulled my network connection, reconnected it, and now my computer received my router's IPv6 address for DNS, but IPv4 DNS servers point to the DNS servers I've specified in the router.

                      For reference, my DHCPv6/RA setting is Managed.

                      The S in IOT stands for Security

                      1 Reply Last reply Reply Quote 0
                      • E
                        emce
                        last edited by

                        Upgraded from 2.1.5 to:

                        2.2-BETA (i386)
                        built on Fri Sep 19 23:33:28 CDT 2014

                        Disabled DNS Forwarder and enabled DNS Resolver.  The service failed to start up with the following error:

                         php-fpm[38680]: /services_unbound.php: The command '/usr/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1411217151] unbound[40074:0] fatal error: user 'unbound' does not exist.'
                        
                        

                        I decided to create an unbound user/group to see what would happen, but upon attempting to start it up again, I received this error:

                        php-fpm[26599]: /services_unbound.php: The command '/usr/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was ''
                        
                        

                        I haven't had a chance to troubleshoot further, but I'm happy to provide any other info.

                        Thanks!
                        -Mike

                        1 Reply Last reply Reply Quote 0
                        • rbgargaR
                          rbgarga Developer Netgate Administrator
                          last edited by

                          @emce:

                          Upgraded from 2.1.5 to:

                          2.2-BETA (i386)
                          built on Fri Sep 19 23:33:28 CDT 2014

                          Disabled DNS Forwarder and enabled DNS Resolver.  The service failed to start up with the following error:

                           php-fpm[38680]: /services_unbound.php: The command '/usr/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1411217151] unbound[40074:0] fatal error: user 'unbound' does not exist.'
                          
                          

                          I decided to create an unbound user/group to see what would happen, but upon attempting to start it up again, I received this error:

                          php-fpm[26599]: /services_unbound.php: The command '/usr/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was ''
                          
                          

                          I haven't had a chance to troubleshoot further, but I'm happy to provide any other info.

                          Thanks!
                          -Mike

                          I pushed an upgrade code to migrate unbound package configuration to 2.2 when it's installed, and also make sure unbound user is created during upgrade. It'll be available on next snapshots.

                          Renato Botelho

                          1 Reply Last reply Reply Quote 0
                          • E
                            emce
                            last edited by

                            @Renato:

                            I pushed an upgrade code to migrate unbound package configuration to 2.2 when it's installed, and also make sure unbound user is created during upgrade. It'll be available on next snapshots.

                            Upgraded to:

                            2.2-BETA (i386)
                            built on Wed Sep 24 04:55:10 CDT 2014
                            FreeBSD 10.1-PRERELEASE

                            And everything is looking good so far.  Thanks!
                            -Mike

                            1 Reply Last reply Reply Quote 0
                            • Raul RamosR
                              Raul Ramos
                              last edited by

                              @emce:

                              Upgraded to:

                              2.2-BETA (i386)
                              built on Wed Sep 24 04:55:10 CDT 2014
                              FreeBSD 10.1-PRERELEASE

                              And everything is looking good so far.  Thanks!
                              -Mike

                              2.2-BETA (amd64)
                              built on Wed Sep 24 04:53:53 CDT 2014 (nanobsd)

                              I continue with some problems:

                              • I have to put on "DHCP Server  -> DNS servers"  my localhost IP, otherwise clients don't pick local DNS server and if i don't have DNS servers in "System ->General", does not get any . "Do not use the DNS Forwarder as a DNS server for the firewall" are uncheck. DNS Forward work ok,

                              • One more time, Aliases in  Host override don't work,

                              • Can't redirect multiple custom domains to a local IP. Ex. mydomain.com and www.mydomain.com, only the top work the other get a non-authorirative sever to get IP if have any.

                              Cya

                              pfSense:
                              ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                              Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                              NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                              1 Reply Last reply Reply Quote 0
                              • P
                                priller
                                last edited by

                                First a little background and then what the problem is and why ….

                                2.2-BETA (amd64)
                                built on Fri Oct 17

                                Behavior of Enabling Forwarding Mode

                                Services: DNS Resolver

                                Select: Enable Forwarding Mode

                                This adds the following to /etc/unbound/unbound.conf

                                # Forwarding
                                forward-zone:
                                    name: "."
                                        forward-addr: 8.8.8.8
                                

                                The forwarding DNS server is read from what is configured in "System: General Setup - DNS servers"

                                This works fine.  However, that is not the sever I want to forward to.

                                What I want to accomplish

                                I want to use unbound to forward to a DNSCrypt Proxy listening on 127.0.0.1 port 40.

                                I am doing this today with DNS Forwarder (dnsmasq) as documented in:
                                https://forum.pfsense.org/index.php?topic=78446.msg453441#msg453441

                                Attempted configuration

                                Since using the "Enable Forwarding Mode" checkbox picks the DNS servers in General Setup, I need a way to override that and use 127.0.0.1@40.

                                So, I deselected "Enable Forwarding Mode" and in the Advanced box entered:

                                forward-zone:
                                    name: "."
                                        forward-addr: 127.0.0.1@40
                                

                                That Advanced configuration shows in /conf/config.xml.  BUT, unbound never uses it and is not in forwarding mode.

                                Since that is a valid unbound configuration , why is it being ignored when you enter it in the Advanced box?  Shouldn't these options be passed to unbound when it starts?

                                1 Reply Last reply Reply Quote 0
                                • Raul RamosR
                                  Raul Ramos
                                  last edited by

                                  Hi

                                  Someone please :), correct host overrides? thanks.

                                  pfSense:
                                  ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                                  Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                                  NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                                  1 Reply Last reply Reply Quote 0
                                  • R
                                    router_wang
                                    last edited by

                                    The resolver is forwarding requests to my providers DNS instead of querying the root domain name servers. You can test this by going to https://www.dnsleaktest.com/

                                    How can I configure it not to do this?

                                    1 Reply Last reply Reply Quote 0
                                    • chpalmerC
                                      chpalmer
                                      last edited by

                                      @router_wang:

                                      The resolver is forwarding requests to my providers DNS instead of querying the root domain name servers. You can test this by going to https://www.dnsleaktest.com/

                                      How can I configure it not to do this?

                                      Go to System/General Setup-  DNS Servers…

                                      Uncheck- " Allow DNS server list to be overridden by DHCP/PPP on WAV"

                                      Check-  "Do not use the DNS Forwarder as a DNS server for the firewall"

                                      Triggering snowflakes one by one..
                                      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                      1 Reply Last reply Reply Quote 0
                                      • R
                                        router_wang
                                        last edited by

                                        @chpalmer:

                                        @router_wang:

                                        The resolver is forwarding requests to my providers DNS instead of querying the root domain name servers. You can test this by going to https://www.dnsleaktest.com/

                                        How can I configure it not to do this?

                                        Go to System/General Setup-  DNS Servers…

                                        Uncheck- " Allow DNS server list to be overridden by DHCP/PPP on WAV"

                                        Check-  "Do not use the DNS Forwarder as a DNS server for the firewall"

                                        Yes, I have it set like this and it still does it anyway.

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          athurdent
                                          last edited by

                                          I'm using CARP virtual IPs and run Unbound on "All" interfaces.
                                          If I query the CARP IP from a Linux box, I get this:

                                          root@none:~# dig @192.168.xxx.254 www.heise.de
                                          ;; reply from unexpected source: 192.168.xxx.5#53, expected 192.168.xxx.254#53
                                          ;; reply from unexpected source: 192.168.xxx.5#53, expected 192.168.xxx.254#53
                                          ;; reply from unexpected source: 192.168.xxx.5#53, expected 192.168.xxx.254#53
                                          

                                          Snapshot is AMD64 from today.

                                          1 Reply Last reply Reply Quote 0
                                          • H
                                            Hugovsky
                                            last edited by

                                            @router_wang:

                                            @chpalmer:

                                            @router_wang:

                                            The resolver is forwarding requests to my providers DNS instead of querying the root domain name servers. You can test this by going to https://www.dnsleaktest.com/

                                            How can I configure it not to do this?

                                            Go to System/General Setup-  DNS Servers…

                                            Uncheck- " Allow DNS server list to be overridden by DHCP/PPP on WAV"

                                            Check-  "Do not use the DNS Forwarder as a DNS server for the firewall"

                                            Yes, I have it set like this and it still does it anyway.

                                            Are you using dhcp? if yes, you have to put the ip from the interface you're using in dns servers so it can be assigned to leases.

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