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

    DNS Resolver

    2.2 Snapshot Feedback and Problems - RETIRED
    44
    186
    124.7k
    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
      phil.davis
      last edited by

      The code in /etc/inc/unbound.inc simply does not implement the settings into the conf file.
      I am looking at this. It will be easy to finish the implementation - pull request in 1 hour hopefully.

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        Pull request: https://github.com/pfsense/pfsense/pull/1336

        That makes it implement all the parameters that can be specified in the "Advanced" section (the custom options box) and on the "Advanced" tab. unbound.conf has all this stuff now after pressing Apply.

        And it took me 72 minutes between posts - there were a few little extra bits to think about, software project estimation is never an exact science, and I actually tested it also  ;)

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

          Thanks again for being so fast. I'll test it and report back.

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

            It's working perfectly on the latest snapshot. Thanks again. Although, I was reading unbound docs and noticed this:

            "FILE FORMAT
                  There  must be whitespace between keywords. Attribute keywords end with a colon ':'. An attribute is followed by its containing attributes, or a value."

            Text parsed in the advanced field breaks the line with spaces. Do you think this is important?

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

              Phil and Hugovsky, thanks for following up on this. I know it's community so it's awesome you helped out with this.
              Will test it shortly.

              Cheers.

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

                @athurdent:

                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.

                I took another look at this:

                IP aliases can be explicitly chosen in the GUI but do not appear in unbound.conf so this does not help with the problem. Seems like a bug and should be fixed I guess.

                If you set

                interface-automatic: yes

                then it replies properly when doing a dig@ the alias IP.
                This feature is marked experimental though, I don't know the downsides.

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

                  Hi

                  I've another issue, all my DHCP6 static bindings are not included in /var/unbound/host_entries.conf. It shows only the IPv4 entries.

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

                    file a bug.

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

                      @gonzopancho:

                      file a bug.

                      Bug #4013

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

                        Most things should be fixed here now. Open DNS Resolver bug tickets can be viewed here:
                        https://redmine.pfsense.org/projects/pfsense/issues?query_id=42

                        if you notice anything not on the list, please post here on this board, either in this thread or start your own. If you have a clearly-defined bug report, open a ticket at redmine.pfsense.org. If you're not sure the specific issue, it's best to discuss here first, where someone can help quantify the issue.

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

                          Does not seem to work properly with IP Aliases or CARP interfaces here. IP Aliases don't work at all, CARP virtual IPs create an interface entry with "Array" and unbound fails to start.

                          To reproduce:
                          -create an IP Alias
                          -choose it as the only Network interface in Unbound
                          Result in /var/unbound/unbound.conf

                          # Interface IP(s) to bind to

                          Or:
                          -create a CARP virtual IP
                          -choose it as the only Network interface in Unbound
                          Result in /var/unbound/unbound.conf

                          # Interface IP(s) to bind to
interface: 192.168.xxx.6
interface: Array

                          I'm testing on the latest:

                          2.2-BETA (amd64) 
built on Mon Nov 17 19:31:46 CST 2014 
FreeBSD 10.1-RELEASE
                          1 Reply Last reply Reply Quote 0
                          • P
                            phil.davis
                            last edited by

                            cmb fixed that "Array" thing with very recent commit https://github.com/pfsense/pfsense/commit/845fd268c94e3c4de31700ce29963038e28fa017
                            But I suspect that now you might just get no binding.
                            You could install the latest /etc/inc/unbound.inc and then report back what remains wrong.

                            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                              Thanks Phil!
                              CARP seems to work Ok now, also verified that it can be queried with dig@.
                              An IP alias still behaves as described above.

                              1 Reply Last reply Reply Quote 0
                              • D
                                dstroot
                                last edited by

                                Used to do this with dnsmasq:

                                Insert the following into the “Advanced” text area field on the DNS Forwarder page in pfSense:  bogus-nxdomain=92.242.140.2

                                This stopped my ISP from hijacking DNS.

                                Doesn't seem to work with unbound.  Is there an equivalent command?  If I put it in the unbound advanced box unbound dies.

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

                                  I don't see an equivalent to that with Unbound. Though if you have Unbound doing its own recursion (don't enable forwarding mode), you should never see that from your ISP.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    dstroot
                                    last edited by

                                    @CMB - thanks for the swift response.  I know you are working at banging out 2.2.

                                    Can you elaborate what "forwarding mode" does for unbound?  I want unbound to cache DNS queries and be the DNS server for my LAN.  I was under the impression I needed it on so unbound would be a cache server and "forward" the results of my main DNS servers (for example say 8.8.8.8).

                                    BTW I did turn forwarding off to see what happens and the DNS hijacking stopped.  Thx for that tip!

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      phil.davis
                                      last edited by

                                      Forwarding mode means it will just send queries (for domains not already in the cache) directly upstream to the defined upstream DNS server/s it has been told about.
                                      With recursion, unbound does its queries directly through the chain of internet root servers down to the authoritative server for the requested domain, thus avoiding using some intermediate upstream DNS and its cache, but keeps a cache for itself.
                                      http://en.wikipedia.org/wiki/Domain_Name_System#Recursive_and_caching_name_server

                                      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        dstroot
                                        last edited by

                                        So it caches either way?

                                        So what is the use case for the forwarder option?  To force something like OpenDNS?  Because it sounds as if the non-forwarder behavior is the most accurate option, no?  (maybe slower?).

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          phil.davis
                                          last edited by

                                          For example, I subscribe to the DynDNS "Internet Guide" service (it is cheap for 10 public IPs). So it can filter name responses for categories of sites (porn, violent…). That does a good job of keeping staff away from that sort of content.
                                          So I want the pfSense DNS to just forward to DynDNS servers, because I really do want a changed (filtered) view of what the real root servers have.

                                          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            phil.davis
                                            last edited by

                                            DNS Forwarder Host Overrides - the aliases (if any) of the main host override display on the main screen, in addition to the main override entry itself.
                                            DNS Resolver Host Overrides - the aliases (if any) of the main host override do not display on the main screen. Only the main override entry itself is displayed.
                                            It is not effecting what is stored in the actual config. When you edit a DNS Resolver Host Override the aliases are there.

                                            Does anybody care?
                                            Leave it as it is?

                                            DNS-Forwarder-Host-Overrides.png
                                            DNS-Forwarder-Host-Overrides.png_thumb
                                            DNS-Resolver-Host-Override-entry.png
                                            DNS-Resolver-Host-Override-entry.png_thumb
                                            DNS-Resolver-Host-Overrides.png
                                            DNS-Resolver-Host-Overrides.png_thumb

                                            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post