PTR delegation 16 IPs

Barry Margolin barmar at bbnplanet.com
Wed Jan 19 15:07:21 UTC 2000


   Date: Wed, 19 Jan 2000 14:07:41 +0100
   From: Christian Krackowizer <kra1 at technodat.co.at>

   At 16:37 18.01.2000 +0000, you wrote:
   >In article <4.3.0.29.0.20000118165829.00bb84b0 at hpwp3.technodat.co.at>,
   >Christian Krackowizer  <kra1 at technodat.co.at> wrote:
   > >well, our german division also has 16 adresses only: 193.100.177.32/28
   > >I tried both forms, zone is loaded, the (new created) files.rev on the
   > >secondary do show all nodes, but an 'arp -a' cannot resolve to names.
   > >Now running as 'full' C-network, also defining only our 16 adresses works.
   > >Files.rev looks nearly the same, only $ORIGIN ... is changed.
   > >? is this an 'arp' problem or were should I look ?
   >
   >The 177.100.193.in-addr.arpa zone isn't delegated to you in the first
   >place.

   Sorry, I don't understand. We are authoritive for 'technodat.de' and use
   193.100.177.32/28. Primary NS is in Austria, secondary in Germany at the
   location of 'technodat.de'.

The organization that's authoritative for 100.193.in-addr.arpa has to
delegate authority for 32-28.177.100.193.in-addr.arpa to your name servers.
Otherwise, no one will know to go to your servers for this subdomain -- DNS
lookups work by starting at the root and following chains of delegation of
subdomains.  If a delegation is missing, it breaks the chain.

   When I setup a '177.100.193.in-addr.arpa' zone containing IP's 32-47, an
   'arp -a' on the Secondary can resolve all addresses and shows the names.
   Changing to '32-47.177.100.193.in-addr.arpa' zone containing the same IP's
   cannot be resolved on the same machine !?
   (in this short description I didn't mention all things like changing the
   files, changing $ORIGIN, changing serial number, ndc reloads etc ...)

Classless in-addr.arpa depends on the parent domain containing a bunch of
CNAME records.  It's not enough that you have the
32-47.177.100.193.in-addr.arpa zone on your server, the server for
177.100.193.in-addr.arpa has to have a bunch of CNAME records that look
like:

32 CNAME 33.32-47
33 CNAME 34.32-47
and so on.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA



More information about the bind-users mailing list