PTR zone /28 not working

Chris Thompson cet1 at cam.ac.uk
Thu Nov 5 19:47:29 UTC 2009


On Nov 5 2009, joans4nz wrote:

>Hi,
>
>Thank you Mr Mark Andrews for your answer, and yes, I want help. I am sorry
>about my first message, I repeat bellow, so I change all
>CCC.BBB.AAA.in-addr.arpa's to my real numbers. 

That certainly helps. Look at this:

$ dig +trace soa 224/28.66.6.190.in-addr.arpa.

; <<>> DiG 9.7.0b1 <<>> +trace soa 224/28.66.6.190.in-addr.arpa.
;; global options: +cmd
.                       318331  IN      NS      F.ROOT-SERVERS.NET.
.                       318331  IN      NS      M.ROOT-SERVERS.NET.
.                       318331  IN      NS      J.ROOT-SERVERS.NET.
.                       318331  IN      NS      E.ROOT-SERVERS.NET.
.                       318331  IN      NS      B.ROOT-SERVERS.NET.
.                       318331  IN      NS      A.ROOT-SERVERS.NET.
.                       318331  IN      NS      K.ROOT-SERVERS.NET.
.                       318331  IN      NS      D.ROOT-SERVERS.NET.
.                       318331  IN      NS      G.ROOT-SERVERS.NET.
.                       318331  IN      NS      C.ROOT-SERVERS.NET.
.                       318331  IN      NS      H.ROOT-SERVERS.NET.
.                       318331  IN      NS      L.ROOT-SERVERS.NET.
.                       318331  IN      NS      I.ROOT-SERVERS.NET.
;; Received 376 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

190.in-addr.arpa.       86400   IN      NS      SEC3.APNIC.NET.
190.in-addr.arpa.       86400   IN      NS      NS3.AFRINIC.NET.
190.in-addr.arpa.       86400   IN      NS      NS2.LACNIC.NET.
190.in-addr.arpa.       86400   IN      NS      NS-SEC.RIPE.NET.
190.in-addr.arpa.       86400   IN      NS      NS2.DNS.BR.
190.in-addr.arpa.       86400   IN      NS      NS.LACNIC.NET.
190.in-addr.arpa.       86400   IN      NS      TINNIE.ARIN.NET.
;; Received 218 bytes from 192.228.79.201#53(B.ROOT-SERVERS.NET) in 175 ms

66.6.190.in-addr.arpa.  86400   IN      NS      ns1.etecsa.net.
66.6.190.in-addr.arpa.  86400   IN      NS      ns2.etecsa.net.
;; Received 92 bytes from 2001:dc0:1:0:4777::140#53(SEC3.APNIC.NET) in 312 ms

224/28.66.6.190.in-addr.arpa. 2000 IN   NS      ns1.mincex.cu.66.6.190.in-addr.arpa.
224/28.66.6.190.in-addr.arpa. 2000 IN   NS      ns2.mincex.cu.66.6.190.in-addr.arpa.
;; Received 92 bytes from 200.55.128.4#53(ns2.etecsa.net) in 676 ms

;; connection timed out; no servers could be reached

The delegation of 224/28.66.6.190.in-addr.arpa from 66.6.190.in-addr.arpa
has been mangled. It reports the authoritative nameservers for the subzone
as

   ns1.mincex.cu.66.6.190.in-addr.arpa.
   ns2.mincex.cu.66.6.190.in-addr.arpa.

(and of course they do not exist) whereas they are almost certainly
meant to be

   ns1.mincex.cu.
   ns2.mincex.cu.

Classic case of "leaving out the trailing dot".

But even if that were corrected, it turns out that ns1.mincex.cu and
ns2.mincex.cu have never heard of 224/28.66.6.190.in-addr.arpa. and
also have an entirely different version of 66.6.190.in-addr.arpa than
ns1.etecsa.net and ns2.etecsa.net do. You have a lot of errors to
correct.

-- 
Chris Thompson
Email: cet1 at cam.ac.uk



More information about the bind-users mailing list