Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Nov 1999 20:12:39 -0800
From:      "Michael Bryan" <fbsd-isp@ursine.com>
To:        "Bret Ford" <bford@tiger.cc.uop.edu>, freebsd-isp@FreeBSD.ORG
Subject:   Re: Struggling to get in-addr.arpa working
Message-ID:  <199911302012390690.44900211@quaggy.ursine.com>
In-Reply-To: <Pine.GSO.4.20.9911301913540.23060-100000@tiger.cc.uop.edu>
References:  <Pine.GSO.4.20.9911301913540.23060-100000@tiger.cc.uop.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

>Using 'dig @ns1.pbi.net -a 9.57.102.216.in-addr.arpa' and so on, I
>figured out how PacBell Internet has done the delegation:
>
> 9.57.102.216.in-addr.arpa.  2H IN CNAME   9.8.57.105.216.in-addr.arpa.
>10.57.102.216.in-addr.arpa.  2H IN CNAME  10.8.57.105.216.in-addr.arpa.
>11.57.102.216.in-addr.arpa.  2H IN CNAME  11.8.57.105.216.in-addr.arpa.
>12.57.102.216.in-addr.arpa.  2H IN CNAME  12.8.57.105.216.in-addr.arpa.
>13.57.102.216.in-addr.arpa.  2H IN CNAME  13.8.57.105.216.in-addr.arpa.
>14.57.102.216.in-addr.arpa.  2H IN CNAME  14.8.57.105.216.in-addr.arpa.
>
>...which goes from one Class B network to another.

Here's the first problem.  PBI has a typo here.  All of the "105" entries
on the right side should be "102".  You need to contact them and get them
to fix this.  Once they make that correction, then what you have is a new
psuedo-domain, which is 8.57.102.216.in-addr.arpa, based on the first
address in the delegated subnet.  All of your delegated entries are under
that new subdomain.

>zone "8.57.105.216.in-addr.arpa" {
>	type master;
>	file "namedb/db.reverse";
>};

That also needs to be "102", not "105".

>----------------------------------------
>db.reverse
>----------------------------------------
>@			 	IN SOA dante.plover.org. bford.dante.plover.org. (
>				1999113010	; Serial
>				10800		; Refresh after 3 hours
>				3600		; Retry after 1 hour
>				604800		; Expire after 1 week
>				7200 ) 		; Default TTL of 2 hours
>
>				    	   NS	dante.plover.org.
>
>9.57.102.216.in-addr.arpa.	3600	IN PTR  gateway.plover.org.
>10.57.102.216.in-addr.arpa.	3600	IN PTR	heather.plover.org.
>11.57.102.216.in-addr.arpa.	3600	IN PTR 	thorin.plover.org.
>12.57.102.216.in-addr.arpa.	3600	IN PTR	advent.plover.org.
>13.8.57.105.216.in-addr.arpa.	3600	IN PTR	13.57.102.216.in-addr.arpa.
>13.57.102.216.in-addr.arpa.	3600	IN PTR	dante.plover.org.
>14.57.102.216.in-addr.arpa.	3600	IN PTR	daman.plover.org.
>----------------------------------------

That should be as follows:

9.8.57.102.216.in-addr.arpa.	3600	IN PTR	gateway.plover.org.
10.8.57.102.216.in-addr.arpa.	3600	IN PTR	heather.plover.org.
11.8.57.102.216.in-addr.arpa.	3600	IN PTR 	thorin.plover.org.
12.8.57.102.216.in-addr.arpa.	3600	IN PTR	advent.plover.org.
13.8.57.102.216.in-addr.arpa.	3600	IN PTR	dante.plover.org.
14.8.57.102.216.in-addr.arpa.	3600	IN PTR	daman.plover.org.


So the answer is, fix the zone to be "102", not "105", make the
given changes above within that zone (you have to have the "8"
subdomain present), and notify PBI of their mistake.  Once they
have fixed their mistake, everything should be normal.  I already
checked, and they -do- delegate 8.57.102.216.in-addr.arpa to 
your system:

  8.57.102.216.in-addr.arpa.  1H IN NS  dante.plover.org.

Then when a lookup is done, say on "9.57.102.216.in-addr.arpa",
the following effectively describes what will happen:

    1) A resolver will determine that PBI's nameservers are
       authoritative for 57.102.216.in-addr.arpa, and send
       the request there.

    2) It will get back this CNAME record:

	      9.57.102.216.in-addr.arpa   CNAME  9.8.57.102.216.in-addr.arpa

    3) It will then discover that your system (dante.plover.org) is
       authoritative for the domain 8.57.102.216.in-addr.arpa, and
       do a lookup on 9.8.57.102.216.in-addr.arpa with your server.

    4) It will then get back the PTR record you have setup.


All lookups will eventually come to your system.  You might want
to see if PBI will also act as secondaries for the delegated domain,
so reverse lookups can be handled by their nameservers, but that's
not strictly necessary.  It just provides backup service if your
system is not available at some point, and is probably a good idea.

Hope this helps...


Michael Bryan
fbsd-isp@ursine.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911302012390690.44900211>