DNS Resolver

wagonza · Jun 19, 2014, 8:07 PM

Hi guys

in 2.2 the DNS forwarder is looking to be replaced and thus DNS Resolver has been added. It does require more testing than what I have and some others have done.
Please could you test it and provide feedback.

Thanks

m3usv0x · Jun 22, 2014, 1:01 AM

Settings do not stick under "advanced".
Attempted even checking random radio boxes and saving, same effect.

m3usv0x · Jun 23, 2014, 5:15 PM

Getting this for awhile now:
dhcpleases: Could not deliver signal HUP to process because its pidfile does not exist, No such process.

ankaerith · Jun 24, 2014, 5:10 AM

@m3usv0x:

Settings do not stick under "advanced".
Attempted even checking random radio boxes and saving, same effect.

For what it is worth, I see the same issue.

Raul Ramos · Jul 9, 2014, 10:59 AM

Hi

Settings does not stick only on advanced, in general settings happens to.
I can't create a domain like mycustomdomain.com (10.0.0.50) and www.mycustomdomain.com (10.0.0.50) in Host Overrides, only one works. DNS Forward works OK
Can't delete networks when edit one access list.
I have a warning on Boot /etc/inc/unbund.inc file don't existe but /etc/inc/unbund.inc exist, i don't know if is a Caps problem Edited: The warning is not for file Unbund.inc is for unbund.inc no Caps
Updating to 5 July from a a week ago seems having problems find some hosts, don't know why. I have to change to DNS Forward to solve this problems. One example i put the pfsense host name on Overrides and fail to resolve, some other works. The only change i make is using Vlans

2.2-ALPHA (amd64) Full with RAM Disks enable.
built on Sat Jul 05 16:00:36 CDT 2014
FreeBSD 10.0-STABLE

feld · Jul 9, 2014, 1:44 AM

Settings aren't sticking

Can't resolve anything unless I disable forwarders

Disabling forwarders breaks my ability to forward domains to certain servers

athurdent · Jul 17, 2014, 8:07 AM

Just tried the latest build:

2.2-ALPHA (amd64) 
built on Wed Jul 16 09:13:49 CDT 2014

Looks better than before. I disabled forwarding mode since I want unbound to do the DNS lookups itself. It starts and does DNS lookups now. As soon as I set an outgoing interface it does not work anymore. I set it to WAN, which is the test hosts only WAN interface, configured to do DHCP/DHCPv6. Looking at the config file it seems that this interface cannot be found/parsed somehow:

# Outgoing interfaces to be used
outgoing-interface:

stompro · Jul 19, 2014, 12:03 AM

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

drclaw · Jul 19, 2014, 3:55 AM

It doesn't seem to be picking up the aliases set for a host - creates the original ok, but not the aliases… I tried creating 1-5 for a few of my hosts, none of them work.

FreeBSD pfsense 10.0-STABLE FreeBSD 10.0-STABLE #18 0d8378f(HEAD)-dirty: Mon Jul 14 10:18:35 CDT 2014 root@pf22-amd64-snap:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64

[2.2-ALPHA][admin@pfsense]/etc/unbound(49): unbound -v
[1405742091] unbound[56768:0] notice: Start of unbound 1.4.20.

wagonza · Jul 19, 2014, 10:52 AM

@m3usv0x:

Settings do not stick under "advanced".
Attempted even checking random radio boxes and saving, same effect.

This should be fixed.

wagonza · Jul 19, 2014, 10:59 AM

@mais_um:

Hi

Settings does not stick only on advanced, in general settings happens to.

This should be fixed.

@mais_um:

I can't create a domain like mycustomdomain.com (10.0.0.50) and www.mycustomdomain.com (10.0.0.50) in Host Overrides, only one works. DNS Forward works OK

Ok will look into this.

@mais_um:

Can't delete networks when edit one access list.

Please check latest snapshot.

@mais_um:

I have a warning on Boot /etc/inc/unbund.inc file don't existe but /etc/inc/unbund.inc exist, i don't know if is a Caps problem Edited: The warning is not for file Unbund.inc is for unbund.inc no Caps

I dont see this error but check if it happens for you in latest snap.

@mais_um:

@mais_um:

Updating to 5 July from a a week ago seems having problems find some hosts, don't know why. I have to change to DNS Forward to solve this problems. One example i put the pfsense host name on Overrides and fail to resolve, some other works. The only change i make is using Vlans

2.2-ALPHA (amd64) Full with RAM Disks enable.
built on Sat Jul 05 16:00:36 CDT 2014
FreeBSD 10.0-STABLE

Hrmm.. once you make the change and it stops resolving then could please PM me your unbound config file so I can see if anything is missing?

wagonza · Jul 19, 2014, 10:59 AM

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

wagonza · Jul 19, 2014, 11:02 AM

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

Raul Ramos · Jul 22, 2014, 9:56 AM

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.

Aug 4, 2014, 4:18 AM

@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

m3usv0x · Aug 9, 2014, 3:02 AM

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

MikeV7896 · Aug 31, 2014, 2:16 AM

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

grandrivers · Aug 31, 2014, 3:01 AM

yes i noticed this also in 2.1.4 when doing some troubleshooting

Fegu · Sep 7, 2014, 7:55 PM

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 · Sep 16, 2014, 11:05 PM

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.