yet another reverse dns problem...

[Kevin Darcy]

One of the nameservers for 23.192.200.in-addr.arpa (dnsspo1.netstream.com.br) is giving correct answers for these PTR's, but the other
(dnsrj01.netstream.com.br) is not. Looks like the zone hasn't replicated properly between their servers. They both have a serial # of 1 on the
zone, so either they forgot to increment the serial number on the master, or they're using some out-of-band method of replication which has
apparently malfunctioned.

                                                                                                                                            -
Kevin

Alexandre Florio wrote:

>         Sorry for another reverse DNS misconfig problem, but I've searched the lists and the net but couldn't find the solution... Here it go:
>
> Diagnostics:
>
>         The network block is 200.192.23.0/27;
>         Normal DNS lookups are fine;
>         ISP DNS server is 200.192.1.36;
>         ISP claims it's all correct at his side;
>
>         My ISP instructs me to place the following zone in named.conf (using BIND 8.2.3):
>
>         zone "1-30.23.192.200.in-addr.arpa" IN {
>                 type master;
>                 notify yes;
>                 file "pz/1-30.23.192.200.in-addr.arpa";
>                 allow-transfer {
>                   200.192.1.36;
>         };
>
>         And here is the file pz/1-30.23.192.200.in-addr.arpa:
>
>         @       IN      SOA     ns.cipher.com.br.       root.cipher.com.br. (
>                         2001020507 ; serial
>                         28800 ; refresh
>                         7200 ; retry
>                         1W ; expire
>                         86400) ; default_ttl
>                 NS      ns.cipher.com.br.
>                 NS      dnsspo1.netstream.com.br.
>
>         1       IN      PTR     router.cipher.com.br.
>         2       IN      PTR     kerberos.cipher.com.br.
>         17      IN      PTR     gateway.cipher.com.br.
>         18      IN      PTR     ns.cipher.com.br.
>         19      IN      PTR     server1.cipher.com.br.
>         20      IN              PTR             server2.cipher.com.br.
>         21      IN              PTR             ntint.cipher.com.br.
>         22      IN              PTR             is32.cipher.com.br.
>
> Problem:
>
>         Reverse DNS lookups only works for some randomly hosts at each named initialization:
>
>         $ for a in `echo 1 2 17 18 19 20 21 22`; do host 200.192.23.$a; done
>         1.23.192.200.IN-ADDR.ARPA is a nickname for 1.1-30.23.192.200.IN-ADDR.ARPA
>         1.1-30.23.192.200.IN-ADDR.ARPA domain name pointer router.cipher.com.br
>         Host not found.
>         Host not found.
>         18.23.192.200.IN-ADDR.ARPA is a nickname for 18.1-30.23.192.200.IN-ADDR.ARPA
>         18.1-30.23.192.200.IN-ADDR.ARPA domain name pointer ns.cipher.com.br
>         19.23.192.200.IN-ADDR.ARPA is a nickname for 19.1-30.23.192.200.IN-ADDR.ARPA
>         19.1-30.23.192.200.IN-ADDR.ARPA domain name pointer server1.cipher.com.br
>         20.23.192.200.IN-ADDR.ARPA is a nickname for 20.1-30.23.192.200.IN-ADDR.ARPA
>         20.1-30.23.192.200.IN-ADDR.ARPA domain name pointer server2.cipher.com.br
>         21.23.192.200.IN-ADDR.ARPA is a nickname for 21.1-30.23.192.200.IN-ADDR.ARPA
>         21.1-30.23.192.200.IN-ADDR.ARPA domain name pointer ntint.cipher.com.br
>         22.23.192.200.IN-ADDR.ARPA is a nickname for 22.1-30.23.192.200.IN-ADDR.ARPA
>         22.1-30.23.192.200.IN-ADDR.ARPA domain name pointer is32.cipher.com.br
>
>         (missed .2 and .17 hosts)
>         My resolv.conf is allright (nameserver 200.192.23.18).
>
>         Does anybody knows what can be going on?
>         (ask me if you need more info about config.)
>
> Thanx,
> Alexandre Florio