Bind 9.9 upgrade and RFC 1918 Errors
Matus UHLAR - fantomas
uhlar at fantomas.sk
Wed Mar 14 12:53:18 UTC 2018
On 14.03.18 04:44, Chris Wilson wrote:
>I just recently upgraded one of our servers to bind 9.9, and I'm having some
>issues.
>
>We have a legacy software application running that likes to see both
>forward/reverse dns, however since the upgrade reverse dns is no longer
>working. We have this server working with DHCPD to automatically update zone
>records.
>When I try to query the server I get:
>
>[root at server1 cswilson]# nslookup 192.160.1.149
>
>** server can't find 149.1.160.192.in-addr.arpa.: NXDOMAIN
are you aware that 192.160.1.149 is NOT a RFC1918 address?
>And in the log:
>
>Mar 14 04:35:06 server1 named[2128]: client 127.0.0.1#44884
>(2.1.168.192.in-addr.arpa): RFC 1918 response from Internet for
>2.1.168.192.in-addr.arpa
bind apparently refused your reverse zones. Try restarting it and see what's
in the logs.
> disable-empty-zone "168.192.in-addr.arpa";
you don't need that. Let BIND create empty 168.192.in-addr.arpa and
configure your zones properly.
>zone "0.1.168.192.in-addr.arpa" {
>
> type master;
>
> file "/var/named/192.168.1.0.rev";
>
> allow-update { key DHCP_UPDATER; };
>
> };
0.1.168.192.in-addr.arpa is only for one IP - 192.168.1.0.
for 192.168.1.0/24 you need reverse zone 1.168.192.in-addr.arpa
--
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"Where do you want to go to die?" [Microsoft]
More information about the bind-users
mailing list