DNS PTR reverse lookups not working for 209.101.124.136
Kevin Darcy
kcd at daimlerchrysler.com
Thu Jun 13 16:24:02 UTC 2002
george.richman at media.net wrote:
> Recently our ISP delegated authority for 124.101.209.in-addr.arpa to
> our nameservers.
>
> Network Solutions lists our nameservers as:
>
> DNS3.MEDIA.NET
> DNS4.MEDIA.NET
>
> Our ISP gives PTR authority to our nameservers for
> 124.101.209.in-addr.arpa to our nameservers:
>
> NS1.MEDIA.NET
> NS2.MEDIA.NET
>
> However, BEAGLE.MEDIA.NET and PUG.MEDIA.NET are the actual host names
> of our real nameservers. Both are using CNAMES of our nameservers.
>
> Do CNAMES cause problems with PTR records authority records? Or is
> there a problem with our config?
>
> Here is our named.conf snippet:
>
> -----------------------------------------------
> zone "124.101.209.in-addr.arpa" in {
> type master;
> file "Primary/255-0.124.101.209.in-addr.arpa";
> allow-transfer { 127.0.0.1; 10.0.0.0/8; 205.214.X.X;
> 205.214.X.X; 209.101.X.X/27; };
> };
>
> Here is our ZONE file:
> -----------------------------------------------
> $TTL 36000
> @ IN SOA media.net. root.media.net. (
> 2002061203 ;serial
> 10800 ;refresh
> 3600 ;retry
> 3600000 ;expire
> 86400 ) ;minimum
>
> $ORIGIN 124.101.209.in-addr.arpa.
>
> IN NS beagle.media.net.
> IN NS pug.media.net.
>
> 0 IN PTR net1.media.net.
> 1 IN PTR mn-gw1.media.net.
> 2 IN PTR rs-gw1.media.net.
> 3 IN PTR brd1.media.net.
> 4 IN PTR net2.media.net.
> 5 IN PTR mn-gw2.media.net.
> 6 IN PTR cs-gw2.media.net.
> 7 IN PTR brd2.media.net.
> 8 IN PTR net3.media.net.
> 9 IN PTR mn-gw3.media.net.
> .... etc...
> -----------------------------------------
>
> I do not know why this is not working. Am I losing my mind???
Perhaps :-)
Pointing NS records at CNAMEs is illegal and problematic, but it appears
that you don't have this problem:
% dig -x 209.101.124 @AUTH1.NS.ENI.NET.
; <<>> DiG 8.3 <<>> -x @AUTH1.NS.ENI.NET.
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;; 124.101.209.in-addr.arpa, type = ANY, class = IN
;; ANSWER SECTION:
124.101.209.in-addr.arpa. 4H IN NS beagle.media.net.
124.101.209.in-addr.arpa. 4H IN NS pug.media.net.
;; AUTHORITY SECTION:
124.101.209.in-addr.arpa. 4H IN NS beagle.media.net.
124.101.209.in-addr.arpa. 4H IN NS pug.media.net.
;; ADDITIONAL SECTION:
beagle.media.net. 2h52m55s IN A 209.101.124.134
pug.media.net. 1d6h31s IN A 209.101.124.135
;; Total query time: 28 msec
;; FROM: fxiod01.is.chrysler.com to SERVER: AUTH1.NS.ENI.NET.
205.214.45.6
;; WHEN: Thu Jun 13 12:22:51 2002
;; MSG SIZE sent: 42 rcvd: 150
%
I can even resolve your PTRs...
- Kevin
More information about the bind-users
mailing list