DNS Resolver Host Override not working in Windows
-
So you have something else listening on 53 on pfsense then and not unbound..
lets see what is listening on 53
[2.4.4-RELEASE][admin@sg4860.local.lan]/: sockstat | grep :53 unbound unbound 42007 3 udp4 192.168.3.253:53 *:* unbound unbound 42007 4 tcp4 192.168.3.253:53 *:* unbound unbound 42007 5 udp6 2001:470:snipped:3::253:53 *:* unbound unbound 42007 6 tcp6 2001:470:snipped:3::253:53 *:* unbound unbound 42007 7 udp4 192.168.9.253:53 *:* unbound unbound 42007 8 tcp4 192.168.9.253:53 *:* unbound unbound 42007 9 udp4 192.168.2.253:53 *:* unbound unbound 42007 10 tcp4 192.168.2.253:53 *:* unbound unbound 42007 11 udp4 192.168.6.253:53 *:* unbound unbound 42007 14 tcp4 192.168.6.253:53 *:* unbound unbound 42007 15 udp4 192.168.4.253:53 *:* unbound unbound 42007 16 tcp4 192.168.4.253:53 *:* unbound unbound 42007 17 udp4 192.168.7.253:53 *:* unbound unbound 42007 18 tcp4 192.168.7.253:53 *:* unbound unbound 42007 19 udp4 127.0.0.1:53 *:* unbound unbound 42007 20 tcp4 127.0.0.1:53 *:* unbound unbound 42007 21 udp6 ::1:53 *:* unbound unbound 42007 22 tcp6 ::1:53 *:* [2.4.4-RELEASE][admin@sg4860.local.lan]/: -
@johnpoz said in DNS Resolver Host Override not working in Windows:
sockstat | grep :53
You are right. seems BIND is running.
But I checked the settings and it's disabled.
And what is this "named"???
-
named is BIND
-
Thank you so much, johnpoz!
I manually stopped the service at Status/Services screen. And this is what I got:
c:\>nslookup www.facebook.com Server: pfSense.mydomain.com Address: 192.168.100.2 Name: www.facebook.com Address: 192.168.100.201 c:\>nslookup 192.168.100.201 Server: pfSense.mydomain.com Address: 192.168.100.2 Name: www.facebook.com Address: 192.168.100.201Still have questions though:
-
As the screenshot shows, BIND is NOT enabled. How did this service get started?
-
I haven't touched BIND for a long time. But I did restart pfsense for testing, which means the named service get auto started when reboot. How can I stop it?
-
-
No idea... Seems like you config is borked.. Export your config and look at the xml.. If not enable it shouldn't be starting - unless you manually did something like installed bind on your own vs packages, etc.
-
@johnpoz said in DNS Resolver Host Override not working in Windows:
No idea... Seems like you config is borked.. Export your config and look at the xml.. If not enable it shouldn't be starting - unless you manually did something like installed bind on your own vs packages, etc.
I installed BIND from package. I guess I will have to uninstall it later.
Thank you again for your help! You are amazing! -
Did you maybe click on the service and start it that way? I have the package installed because time need to play with it to help users.
It doesn't auto start itself..
Learned one thing for sure - check earlier what is actually run if other users have sim issue ;) Would of solved your problem like in step one vs just trusting that all you had running was unbound.
-
@johnpoz
No I didn't start the service manually.
Very weird, isn't it? I would think only one service can be started on one port, 53. Maybe it's a bug of pfsense? LOLOne last question:
DNS forwarder, DNS resolver and BIND all do the same thing and only one should be enabled, correct?Is DNS resolver the best in your opinion?
-
No its not a bug.. look at your bindings.. Your not bound to the same things.
Bind is the king of dns... But you do not need it on pfsense, unbound is fine... I have been managing dns for years and years.. Since back in the bind 4 days. I just use unbound... its all you need for a home setup.
its got pretty much any of the features you could possible need.. Now if wanted to run an authoritative ns, or needed slave ns then I would run bind.
-
@shawn8888 said in DNS Resolver Host Override not working in Windows:
I installed BIND from package.
This would have been a good nugget to know right from the start. At least it's working now.
