Delegating Part Of Class C?

[buffalo at icarus.yml.com]

On Thu, 22 Jul 1999, Joseph S D Yao wrote:

> > to us. (note that given an example IP of 123.123.123.80, I am reversing it
> > to 80.123.123.123.IN-ADDR.ARPA as required) ...
> 
> You really have all three octets the same?  Something like 208.208.208?
> ;-)  I guess reversal is meaningless, then.  ;-}

Well, not exactly, but for example purposes... :-)


> > First, the entry from named.conf:
> > 
> > ------------------------------------
> > // Delegated to us by BigISP for client X.
> > zone "80.xxx.xxx.xxx.IN-ADDR.ARPA" {
> >         type master;
> >         file "db.xxx.xxx.xxx..80"; 
> 				^
> This is not just being picky - but computers are more picky than I
> could ever be.  Is this really two dots in your configuration?  Or did
> you re-type everything, and this is a typo?

Just retyped it, and inserted a typo. It's .80 in the real file. 

> > };
> > ------------------------------------
> > 
> > Now. the db file:
> > 
> > ----------------------------
> > ; primaryNS -- db.xxx.xxx.xxx.80
> > ;
> > ;
> > 80.xxx.xxx.xxx.in-addr.arpa. IN  SOA my.primaryNS.com. buffalo.yml.com. (
> >               1
> >           10800
> >            3600
> >           86400
> >           86400 )
> > 
> > 80.xxx.xxx.xxx.in-addr.arpa.  IN  NS  my.primaryNS.com.
> > 80.xxx.xxx.xxx.in-addr.arpa.  IN  NS  my.secondaryNS.com.
> > 
> > ; .81-.93 were delegated to us by BigISP for use with the machines
> > ; hosted at site "A". This allows us to set up reverse lookup.
> > 
> > 81.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host1.mydomain.com.
> > 82.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host2.mydomain.com.
> > 83.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host3.mydomain.com.
> > 84.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host4.mydomain.com.
> > 85.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host5.mydomain.com.
> > 86.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host6.mydomain.com.
> > 87.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host7.mydomain.com.
> > 88.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host8.mydomain.com.
> > 89.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host9.mydomain.com.
> > 90.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host10.mydomain.com.
> > 91.xxx.xxx.xxx.IN-ADDR.ARPA.            IN  PTR   host11.mydomain.com.
> > 
> > ; end of db.xxx.xxx.xxx.80 on primaryNS
> > 
> > ------------------------------------
> > 
> > My understanding was the this was the way to do it, but if I set it up
> > this way, all lookups I do on xxx.xxx.xxx.81 through xxx.xxx.xxx.93 fail.
> > The log error I get each time I try a lookup with this configuration on
> > (for example) xxx.xxx.xxx.82 is:
> > 
> > --------------------------------------
> > Jul 22 11:32:09 primaryNS named[10281]: dangling CNAME pointer
> > (82.80.xxx.xxx.xxx.in-addr.arpa)
> > --------------------------------------
> 
> Just as it's supposed to.  You have never declared
> "82.80.xxx.xxx.xxx.in-addr.arpa".
>
> > Am I totally screwing this up?
> Yes.

Figures :-)

> or - if for some reason you are morbidly afraid of relative addresses -
> 
> 82.80.xxx.xxx.xxx.in-addr.arpa.         IN  PTR   host1.mydomain.com.

Sure, it takes a little extra time to maintain, but just in case someone
who normally doesn't work on this has to in my place, there's no confusion
about *exactly* what's in the record :-)


> You should already have seen in your 'syslog' output [I did ask you
> about 'syslog' output, didn't I, earlier?] the error messages that tell
> you that 82.xxx.xxx.xxx.in-addr.arpa is in no way, shape, form, or
> stretch of the imagination part of the 80.xxx.xxx.xxx.in-addr.arpa
> domain, and so 'named' was ignoring it.
> 
> ;-)

OK, I've now totally redone all of the entries in the db as specified,
i.e.:

82.80.xxx.xxx.xxx.IN-ADDR.ARPA.   IN PTR   host1.mydomain.com.


However, lookups still fail. Now named says *nothing* in the logs, and I
still get 'server failed' whenever I try to lookup:


Even more confused, but still apreciating the helpful input,

--Duncan