Bug #7382
closed
DNS Forwarder does not resolve DNS names on first boot
Added by Özgür Keleş about 7 years ago.
Updated over 4 years ago.
Affected Architecture:
amd64
Description
"DNS Forwarder (dnsmasq)" service is running at first boot but i am get an error : "dhcpleases Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such file or directory." and pfsense can not resolve the DNS names entered in the "Host Overrides" list under "DNS Forwarder". But when the DNS Forwarder (dnsmasq) is restarted everything works fine. So there is a problem at booting time.
I solved the problem adding the following code to services.inc file.
//log_error("dnsmasq command: {$cmd}");
mwexec_bg($cmd);
unset($args);
sleep(2);
system_dhcpleases_configure();
I can confirm the same behavior. My problem is with Domain Overrides, but I'm assuming the problem is the same.
To confirm the DNS forwarder works great if you simply restart it from the Services -> DNS Forwarder tab in the web interface sometime after boot.
I'm not sure how to log anything useful. I can see the requests being logged with a forwarded request, but no reply. I watched using tcpdump to confirm that the packets are not even going out of the router.
It's worth noting that the server I'm hitting (for just the domain override) is across an OpenVPN tunnel.
- Status changed from New to Closed
Old report and no recent recurrences. DNS Forwarder is no longer the preferred resolver, if it's still and issue with the DNS Resolver, open a fresh issue with more detail.
I can confirm this is still an issue, but am I to understand that DNS Forwarder is no longer supported and that all functionality should be available in DNS Resolver?
I wouldn't say "not supported", but not preferred. We prefer to focus any development toward the DNS Resolver. There are only a couple edge cases where the forwarder can do things the resolver cannot, but the resolver is miles ahead in most other areas. Eventually the DNS Forwarder will be removed, but we haven't reached that point yet.
This is a 2-year old issue that hadn't had any movement or additional recent confirmation, and several releases happened since. I have a VM or two with the forwarder still active and can't reproduce this there.
So if this is still a problem on 2.4.4-p3 or 2.5.0, we'll need a lot more information about the specific configuration that leads to the service not running at startup.
I believe we have one of those edge cases that still requires the forwarder - we need to specify a source IP for host/domain overrides, since they don't seem to route properly across an OpenVPN tunnel otherwise.
I can replicate this issue pretty regularly on several different routers - what log/setting info is helpful to track this down?
Hard to say what will help when we don't have much to go on. You'd pretty much have to setup a lab box and then add bit by bit of your config until you can reproduce the problem. Starting with your full DNS Forwarder configuration. That's better done on a forum thread than here, though. And then once you nail down the minimum settings required to reproduce the issue, post it here.
Also available in: Atom
PDF
Updated by 
Updated by