DNS Resolver

Fegu

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.

MikeV7896

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.

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

rbgarga

@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.

emce

@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

Raul Ramos

@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

priller

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?

Raul Ramos

Hi

Someone please :), correct host overrides? thanks.

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?

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"

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.

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.

Hugovsky

@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.

pyrodex

After each update I've noticed unbound won't start on a reboot. I've got to go in and save the settings and then it will start. Here is what I see in the logs each time:


Nov  1 18:22:07 firewall unbound: [80205:0] error: can't bind socket: Can't assign requested address
Nov  1 18:22:07 firewall unbound: [80205:0] debug: failed address fe80::250:56ff:fe1a:1b1c port 42698

I merely just update and reboot. Then to correct I simply go into the settings and hit SAVE and that lets it recover.

dstroot

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.

This was a key point - thanks.

Tikimotel

DNS Spoofabillity test: https://www.grc.com/dns/dns.htm

DNS Nameserver Access Details
External Ping: ignored (Nice, as it's preferable for it to be less visible.)
External Query: ignored (This means the nameserver is more spoof resistant.)
DNSSEC Security: supported (This server supports improved security standards.)
–-> Alphabetic Case: mixed (Extra bits of entropy are present in these queries!) <---
Extra Anti-Spoofing: unknown (Unable to obtain server fingerprint.)

I've added the options below into the unbound config on my pfsense v2.1.5 in order to get the extra bits of entropy for the alphabetic case test.


use-caps-for-id: yes
val-clean-additional: yes

I wonder if these are available by default, or switchable settings in the new pfsense 2.2 builds?

Quote on the alphabetic case test:

Alphabetic Case:
The DNS system is not sensitive to alphabetic case, so the domain “WWW.GRC.COM” is identical to “www.grc.com”. DNS is designed to ignore but preserve the alphabetic case used in queries and replies. This creates an opportunity for a DNS resolver to add additional unknown bits of “entropy” to its queries by randomly changing the case of any alphabetic characters in the queried domain name. When replies are received, only the valid replying nameserver that received the mixed-case query could know the proper case for its reply. No spoofing server would know. This would give a clever resolver another way to reject spoofed replies. We know of no nameservers that are deliberately mixing case in this way, but through this test we are helping you to keep your eye out for any.

dstroot

Still not seeing host overrides work.


❯ dig doubleclick.net

; <<>> DiG 9.8.3-P1 <<>> doubleclick.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37689
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;doubleclick.net.		IN	A

;; ANSWER SECTION:
doubleclick.net.	3600	IN	A	70.32.146.212

;; Query time: 105 msec
;; SERVER: 192.168.15.1#53(192.168.15.1)
;; WHEN: Sun Nov  9 14:00:46 2014
;; MSG SIZE  rcvd: 49

issue.png_thumb

Hugovsky

It works for me but, I have to send it to 0.0.0.0, not 127.0.0.1.

dstroot

Hmmm - I'm on the latest beta, tried 0.0.0.0 and 127.0.0.1. Still no joy. Will look into this further tomorrow.

dstroot

My bad. I wasn't filling it out correctly - it works if you do it as I show in the attached.

blocked.png_thumb