This is a discussion on Re: DJBDNS DNS reverse delegation of a /29 with SBC/AT&T - Debian ; mark david mcCreary wrote: > I've got a new DSL line with a small static IP address block - > 188.8.131.52/29 > > I have asked AT&T to reverse delegate that to my DNS servers > so that I can ...
mark david mcCreary wrote:
> I've got a new DSL line with a small static IP address block -
> I have asked AT&T to reverse delegate that to my DNS servers
> so that I can correctly resolve the PTR records, and they
> did. They say they are using the Classless Reverse
> Delegation ¡VRFC 2317 (Section 5.2).
> So my first question is what have they called my zone. I
> dig around a little bit, hitting the SBC name server at
> 184.108.40.206, and ask it what it knows about the first
> address in my little subnet.
> ;; QUESTION SECTION:
> ;220.127.116.11.in-addr.arpa. IN ANY
> ;; ANSWER SECTION:
> 18.104.22.168.in-addr.arpa. 7200 IN NS ns.internet-tools.com.
> 22.214.171.124.in-addr.arpa. 7200 IN NS ns2.internet-tools.com.
> 126.96.36.199.in-addr.arpa. 7200 IN NS ns3.internet-tools.com.
> I interpret this to mean that 188.8.131.52.in-addr.arpa is
> the answer, although I don't think this is correct.
It's what they've set up, apparently. I agree it doesn't match anything
I've seen either.
> So I set up these records in TinyDNS.
> However when I query via dig to my servers, I don't get any
> valid answers back.
I've had mixed results (mostly bad) trying to get useful information
from DJBDNS via dig.
I keep a BIND caching server around for that
and a few other reasons. Try host (Debian package bind9-host) or
nslookup. (dig +trace is particularly useful, but fails miserably when
the local resolver is DJBDNS.)
FTR, lookups via the BIND caching server in the office here bring back
correct data according to your TinyDNS snippet above.
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org