Delegating Part Of Class C?
buffalo at icarus.yml.com
buffalo at icarus.yml.com
Thu Jul 22 16:42:23 UTC 1999
On Wed, 21 Jul 1999, Joseph S D Yao wrote:
> One problem is, you're representing the first parts as xxx.xxx.xxx, so
> I can't tell whether you are correctly reversing the parts of the IP
> address or not.
OK, to avoid any confusion, here's the named.conf entry for the subdomain,
and the contents of the db.file for the sub domain that BigISP has
delegated to us.
As a reminder, BigISP has delegated
xxx.xxx.xxx.80 through xxx.xxx.xxx.94
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) And yes, I own and am
authoritative for 'mydomain.com' below. Forward lookups are working
normally:
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";
};
------------------------------------
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)
--------------------------------------
Am I totally screwing this up?
Many thanks for the continuing helpful feedback...
--Duncan
More information about the bind-users
mailing list