Setting a Domain Override in the DNS Resolver stops the service
-
Hi
When I set up a Domain Override in the DNS Resolver, the DNS Resolver stops and it refuses to start.
I have succesfully set up a host override and tested that it works correctly, but I do not really understand why the domain override stops the service. What I should be looking for?
-
I have not seen this, and just tested with 21.02.2 and works fine here..
What are you putting in for a domain override?
here is what I tested with.
-
@johnpoz Hi, thanks for the quick answer.
The domain is "example.com" (but my domain name instead of example, no subdomain or anything else, just a name and .com). The lookup server IP Address is a local IP too.
This is the DNS Resolver log (it starts at 17:11, when it says ubound stopped):
-
And unbound is not running? You show service not running in service stats?
[21.02.2-RELEASE][admin@sg4860.local.lan]/root: unbound-control -c /var/unbound/unbound.conf status version: 1.13.1 verbosity: 2 threads: 4 modules: 2 [ validator iterator ] uptime: 221 seconds options: control(ssl) unbound (pid 37856) is running...
When you do a query to it for same something - your not getting an answer?
$ dig @192.168.9.253 www.google.com ; <<>> DiG 9.16.13 <<>> @192.168.9.253 www.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49943 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 3417 IN A 172.217.4.100 ;; Query time: 0 msec ;; SERVER: 192.168.9.253#53(192.168.9.253) ;; WHEN: Wed Apr 14 09:29:07 Central Daylight Time 2021 ;; MSG SIZE rcvd: 59 -
@johnpoz Confirmed, the DNS resolver (unbound) is not running.
It goes back to running automatically when I delete the domain rewrite and apply the changes.
Also, checked from a computer connected locally and the dns does not resolve.
The pfSense version is 2.5.1.
-
And if you try and manually start it - it fails, any errors in the logs?
Not able to duplicate it.. So some piece of the puzzle is missing to why its doing it on your and not mine.
You could bump the verbosity up in the log, and see it shows you some info that could give a clue to what is going on.
edit: I am running 21.02.2, I could try firing up a 2.5.1 on a vm.. And see if I can duplicate the problem..
-
Have a similar issue, after updating to 2.5.1 today the local unbound server stops working. I can see the starting service in the log
unbound 6609 [6609:0] info: start of service (unbound 1.13.1).but unbound-control -c /var/unbound/unbound.conf status return
unbound-control[53604:0] error: connect: Can't assign requested address for 127.0.0.1 port 953But service is showing the checkmark that it is running. What is really stange that running a netstat -l -n is showing that the DNS server is running
Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address udp6 0 0 ::1.53 *.* udp4 0 0 127.0.0.1.53 *.*Any idea ?
-
@sashli said in Setting a Domain Override in the DNS Resolver stops the service:
Can't assign requested address for 127.0.0.1 port 953
Yeah with that, you have something on 953.. Do you also have the bind package installed.. This has been a known issue for long time that they like to use the same control port.
-
Nope, never installed BIND. I'm on this configuration with unbound since years now and never had any issues. Only have some host overrides in the config.
Only get it working when I use the option "use remote DNS Server, ignore local DNS" but I need some of the host overrides so I switched back to the other system with 2.5.0 at the moment.
So it is definitely an issue with the unbound
-
look to see if anything is running on 953, unbound is going to have problems if something is using 953. Maybe its not bind? But that errors says it couldn't use that port - for some reason..
-
Just did it with manually changing the unbound control-interface config to 0.0.0.0 but for some reason I always get back with the same error.
Unbound is correcty starting and binding the ports but will not answer any requests
sockstat -4 -l | grep unbound unbound unbound 94120 4 udp4 192.168.1.1:53 *:* unbound unbound 94120 4 tcp4 192.168.1.1:53 *:* unbound unbound 94120 8 udp4 127.0.0.1:53 *:* unbound unbound 94120 9 tcp4 127.0.0.1:53 *:* unbound unbound 94120 14 tcp4 127.0.0.1:953 *:*trying to run the control command gets back with the same error.
root: unbound-control -c /var/unbound/unbound.conf status [1618467957] unbound-control[33867:0] error: connect: Can't assign requested address for 127.0.0.1 port 953 -
@sashli said in Setting a Domain Override in the DNS Resolver stops the service:
Can't assign requested address for 127.0.0.1 port 953
Are you running pfblocker?
-
@johnpoz Yes but no DSNBL function enabled. Already red that thread, so this can not be the answer but thanks a lot to share this
-
Do you have pfblocker enabled at all - turn it off.. Kill all your unbound instances..
Do you still have the same problem?
