Unbound is not registering opnsense for reverse lookups

Started by IsaacFL, August 17, 2025, 08:55:38 PM

Previous topic - Next topic
Unbound no longer seems to be registering the opnsense routers interface addresses other than LAN interface.

from the console:
root@OPNsense:~ # dig opnsense.redacted.com a

; <<>> DiG 9.20.11 <<>> opnsense.redacted.com a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64531
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;opnsense.redacted.com.          IN      A

;; ANSWER SECTION:
opnsense.redacted.com.   3600    IN      A       10.23.60.1
opnsense.redacted.com.   3600    IN      A       xx.xx.xx.xx
opnsense.redacted.com.   3600    IN      A       10.23.255.1
opnsense.redacted.com.   3600    IN      A       10.23.10.1
opnsense.redacted.com.   3600    IN      A       10.23.20.1
opnsense.redacted.com.   3600    IN      A       10.23.30.1
opnsense.redacted.com.   3600    IN      A       10.23.40.1
opnsense.redacted.com.   3600    IN      A       10.23.50.1

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sun Aug 17 11:42:58 PDT 2025
;; MSG SIZE  rcvd: 177


now reverse lookup of the LAN interface looks as expected:

root@OPNsense:~ # dig -x 10.23.10.1

; <<>> DiG 9.20.11 <<>> -x 10.23.10.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47286
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;1.10.23.10.in-addr.arpa.       IN      PTR

;; ANSWER SECTION:
1.10.23.10.in-addr.arpa. 3600   IN      PTR     OPNsense.redacted.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sun Aug 17 11:34:21 PDT 2025
;; MSG SIZE  rcvd: 86

But when I do reverse lookup on any other interface it doesnt return the name of the router:
root@OPNsense:~ # dig -x 10.23.20.1

; <<>> DiG 9.20.11 <<>> -x 10.23.20.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26665
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;1.20.23.10.in-addr.arpa.       IN      PTR

;; AUTHORITY SECTION:
10.in-addr.arpa.        10800   IN      SOA     localhost. nobody.invalid. 1 3600 1200 604800 10800

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sun Aug 17 11:35:03 PDT 2025
;; MSG SIZE  rcvd: 111

It acts the same way with ipv6.

This is recent, maybe after last upgrade?

I have switched over to dnsmasq as dhcp server, but I have not forwarded anything to dnsmasq as dns.