Issue with Reverse Zone in Bind
-
I have two zones configured in a view. The forward zone works without issues, changes are also working. However the reverse zone don't seem to play at all, have tested various configurations, see below. Restarted bind, looked for errors or logs and found only this request logged by syslog.
2022-05-03T22:08:38+02:00 May 3 22:08:38 10.101.0.1 named: queries: info: client @0x80709af60 10.101.16.104#60199 (7.16.101.10.in-addr.arpa): view Site101: query: 7.16.101.10.in-addr.arpa IN PTR + (10.101.0.1)
Query is received but not matched, any help is so appreciated
Bind version 9.16_11
Pfsense+ 21.05.2-RELEASEReverse zone
Zone Name: 1.16.101.10
Zone Type: Master
View: Site101
Reverse Zone: Checked
Name Server: 127.0.0.1
Base Domain IP: 10.101.16.1
allow-query: localnets (Has my internal CIDR blocks configured)I've tried two different formats of the PTR record, the default in the UI
<host> IN PTR <ip_address>
And
<last_octet> IN PTR <fqdn>$TTL 43200 ; $ORIGIN 1.16.101.10.in-addr.arpa. ; Database file 1.16.101.10.DB for 1.16.101.10 zone. ; Do not edit this file!!! ; Zone version 2651606715 ; @ IN SOA 127.0.0.1. zonemaster.1.16.101.10. ( 2651606715 ; serial 1d ; refresh 2h ; retry 4w ; expire 1h ; default_ttl ) ; ; Zone Records ; IN NS 127.0.0.1. hass01 IN PTR 10.101.16.7 ; ;custom zone records ; 3 IN PTR nas01.intra.mydomain.local. 7 IN PTR hass01.intra.mydomain.local. 106 IN PTR SonosZP.intra.mydomain.local.
Forward lookups look like this
nslookup hass01 Server: 10.101.0.1 Address: 10.101.0.1#53 Name: hass01.intra.mydomain.local Address: 10.101.16.7
While reverse fails
nslookup 10.101.16.7 Server: 10.101.0.1 Address: 10.101.0.1#53 ** server can't find 7.16.101.10.in-addr.arpa: NXDOMAIN```
-
Anyone that has insight to share about Bind DNS PTR record troubleshooting?