176.176-18.104.22.168.in-addr.arpa ptr, dig -x 22.214.171.124 +trace fails, host 126.96.36.199 works
craig.skinner at lumison.net
Wed Mar 30 07:21:41 UTC 2005
Kevin Darcy wrote:
> RFC 2317 only needs to be used when you want to delegate control of a
> range that does not fall on an octet boundary. /32 is, technically, on
> an octet boundary. You can delegate 188.8.131.52.in-addr.arpa directly
> as a subzone of 233.19.84.in-addr.arpa -- no need for CNAMEs or any of
> that "176-176" rubbish.
Thanks for that, never occured to me that I could simplify for the
unique case of a /32. Obviously the "lowIP-highIP" will apply for
anything inbetween /30 and /25.
> As for why the dig +trace fails, I think it's because there is no
> delegation from 84.in-addr.arpa to 19.84.in-addr.arpa or anything below:
> % dig -x 184.108.40.206 ptr
> ; <<>> DiG 9.2.2rc1 <<>> -x 220.127.116.11 ptr
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31050
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> ;; QUESTION SECTION:
> ;18.104.22.168.in-addr.arpa. IN PTR
> ;; AUTHORITY SECTION:
> 84.in-addr.arpa. 7200 IN SOA ns-pri.ripe.net.
> ops.ripe.net. 2005032970 43200 7200 1209600 7200
> ;; Query time: 37 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Tue Mar 29 19:56:59 2005
> ;; MSG SIZE rcvd: 99
> I guess someone would need to talk to RIPE about that...
Yeah, our Network Administrator was swinging that way too. I'll pass
this from Tech Support to our Hostmaster. Thanks for your help and
confirming our thoughts.
More information about the bind-users