DNSSEC on pfSense
-
Who else here has multiple interfaces and has Unbound listening on them all?
Also anyone here with domain overrides (Services->DNS Forwarder) specified? If so are they working? -
Ok domain overrides are working. I still need to add an option for DNS Rebinding (enabling/disabling) as that was affecting domain overrides.
Currently it is enabled by default.Besides @jlepthien's problem of multiple interfaces been selected and for some unknown reason not been saved - any other requests/problems?
-
hi wagonza, on my side its running fine and stressless. Really a good thing of Software you created! Thanks a lot!!!
I don't have multiple gateways here to test that special funktions. -
Now it is working for me. I found the problem why he wasn't saving all my interfaces to the conf…
When I looked at the logfile I saw the following:
Dec 15 11:59:58 voldemort unbound: [9464:0] error: Could not open autotrust file for writing, /usr/local/etc/unbound/root-trust-anchor: Read-only file systemI am on embedded so I just mounted / rw and then clicked save. I guess you just have to implement the mounting rw on embedded with the Unbound package and everything should be fine then…
-
Oh, but wait. My OpenDNS is not working anymore… I have configured 208.67.222.222 and 208.67.220.220 as my global DNS servers but when Unbound is running, no urls get blocked anymore. Which DNS servers does Unbound contact for resolving?
-
Oh, but wait. My OpenDNS is not working anymore… I have configured 208.67.222.222 and 208.67.220.220 as my global DNS servers but when Unbound is running, no urls get blocked anymore. Which DNS servers does Unbound contact for resolving?
Did you check "Enable forwarding mode" in the unbound configuration screen?
-
No. If you enable DNSSEC one should disable this I read…
-
No. If you enable DNSSEC one should disable this I read…
In that case I think it's one or another. Not really sure to be honest with you. Try enabling the option and test it using the test dnssec page and let us know if it works.
On the other side of the coin, I am not sure if OpenDNS supports DNSSEC? I thought they adopted DNSCurve.
-
Even with the option enabled, I still can access all forbidden websites. Also the DNSSEC test gives me Borat so that is working as well…
-
Unbound up and running here. When I get a chance, I'm going to set up a secondary on another server and have that pull from the pfsense…
-
Yes, this would work fine if you define the servers under services -> dns forwarder.
Hi, Scott. I am now trying to figure out how to do the zone transfer juju. I am a little confused, since I found an info page about Unbound that states specifically that it does NOT support zone transfers. I have seen this elsewhere too… Can someone shed light on this?
-
Even with the option enabled, I still can access all forbidden websites. Also the DNSSEC test gives me Borat so that is working as well…
Go to the Unbound Status page and check the forwards option. It should display the current OpenDNS servers that you are using. From the cmd line you simply issue unbound-control forward - which will display the same info.
-
Hi, Scott. I am now trying to figure out how to do the zone transfer juju. I am a little confused, since I found an info page about Unbound that states specifically that it does NOT support zone transfers. I have seen this elsewhere too… Can someone shed light on this?
Correct - it is essentially a caching name server. There are ways to get it to return certain records for zones but it is not a BIND,DJBDNS,NSD or any of the others. Are you looking for an alternative to the DNS Package?
-
Go to the Unbound Status page and check the forwards option. It should display the current OpenDNS servers that you are using. From the cmd line you simply issue unbound-control forward - which will display the same info.
With both ways I see nothing. On console output it says off (using root hints).
I also tried mounting rw before but that doesn't change anything. -
I would like an authoritative primary server which can do the 'accept registrations for dhcp clients' juju and serve up zone updates to a secondary elsewhere on my LAN.
-
With both ways I see nothing. On console output it says off (using root hints).
I also tried mounting rw before but that doesn't change anything.Hmm try this from the cmd line unbound-control forward 208.67.222.222 208.67.220.220
Let me know what that returns. unbound-control forward should then list these 2 IP addresses as forwarders as your access control should work.
If that all works then I think I know what the problem is.
-
Hmm try this from the cmd line unbound-control forward 208.67.222.222 208.67.220.220
Let me know what that returns. unbound-control forward should then list these 2 IP addresses as forwarders as your access control should work.
If that all works then I think I know what the problem is.
Hey m8. That works! So is it just the GUI that has got problems? Will this stay after a reboot? Or do I need to edit the unbound.conf by hand? But now I DNSSEC does not seem to be working. The http://test.dnssec-or-not.org/ url does not even open…
Also http://www.dnssec-tools.org/testzone/ does not open? Does it open for you?
-
Hey m8. That works! So is it just the GUI that has got problems? Will this stay after a reboot? Or do I need to edit the unbound.conf by hand?
Nah it wont stick after a reboot. Basically the GUI just executes what you typed by hand. There is no config option to specify them.
Ok i pushed a fix - give it a go and let me know how it goes. -
In that case I think it's one or another. Not really sure to be honest with you. Try enabling the option and test it using the test dnssec page and let us know if it works.
On the other side of the coin, I am not sure if OpenDNS supports DNSSEC? I thought they adopted DNSCurve.
As I've written now, it doesn't work. Well and you are right, OpenDNS adopted DNSCurve….
Nah it wont stick after a reboot. Basically the GUI just executes what you typed by hand. There is no config option to specify them.
Ok i pushed a fix - give it a go and let me know how it goes.Will do when the update shows up…
-
In that case I think it's one or another. Not really sure to be honest with you. Try enabling the option and test it using the test dnssec page and let us know if it works.
On the other side of the coin, I am not sure if OpenDNS supports DNSSEC? I thought they adopted DNSCurve.
As I've written now, it doesn't work. Well and you are right, OpenDNS adopted DNSCurve….
Which I am sure they will regret one day…
Will do when the update shows up…
I upped the version number and hopefully also fixed the file system errors.