Class B delegation issues.

Pasika, Paul M [NTWK SVCS] PaulPasika at NMCC.SprintSpectrum.com
Wed Jan 7 21:38:23 UTC 2004


Hello,
I have been having issued delegating the 68.242.0.0/16 class B network
block using bind 8.x.x.  I'm trying to delegate the block from
207.15.68.164 and 207.15.68.36 to 68.28.242.11 and 68.28.250.11.  I have
tried several methods of delegating this entire block and they all have
failed.  Currently I have a ~40% successful forward set up.  I'd like to
try to get it set up correctly and remove the forward.  Here is how the
block is set up and how it's configured today (I know it's not correct).
I'd like to know what would be the best way to delegate this entire
class B to those DNS servers.
[whois.arin.net]

OrgName:    Sprint PCS
OrgID:      SPCS
Address:    12502 Sunrise Valley Dr
City:       Reston
StateProv:  VA
PostalCode: 20191
Country:    US

NetRange:   68.240.0.0 - 68.244.255.255
CIDR:       68.240.0.0/14, 68.244.0.0/16
NetName:    SPRINT-WIRELESS
NetHandle:  NET-68-240-0-0-1
Parent:     NET-68-0-0-0-0
NetType:    Direct Allocation
NameServer: OSSCDNS01.SPCSDNS.NET
NameServer: OSSCDNS02.SPCSDNS.NET
Comment:    ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate:    2003-07-17
Updated:    2003-12-05

OrgTechHandle: DRW52-ARIN
OrgTechName:   Williams, David R
OrgTechPhone:  +1-913-315-4685
OrgTechEmail:  dwilli16 at mail.sprintpcs.com


On OSSCDNS01.SPCSDNS.NET (207.15.68.164):

In named.conf:

zone "242.68.in-addr.arpa" in {
    type forward;
    forward only;
    forwarders { 68.28.242.11; 68.28.250.11; };
};

On chardns01.spcsdns.net (68.28.242.11):
Slaving IPs have been changed.

zone "0.242.68.in-addr.arpa" in {
        type slave;
        file "db.0.242.68.in-addr.arpa";
        masters { 10.255.255.48; };
};

zone "1.242.68.in-addr.arpa" in {
        type slave;
        file "db.1.242.68.in-addr.arpa";
        masters { 10.255.255.48; };
};

zone "2.242.68.in-addr.arpa" in {
        type slave;
        file "db.2.242.68.in-addr.arpa";
        masters { 10.255.255.48; };
};

...

zone "254.242.68.in-addr.arpa" in {
        type slave;
        file "db.254.242.68.in-addr.arpa";
        masters { 10.255.255.48; };
};

zone "255.242.68.in-addr.arpa" in {
        type slave;
        file "db.255.242.68.in-addr.arpa";
        masters { 10.255.255.48; };
};

(slaving is set up properly and is working.)

On atlndns01.spcsdns.net (68.28.250.11):

In named.conf

zone "0.242.68.in-addr.arpa" in {
        type master;
        file "db.0.242.68.in-addr.arpa";
};

zone "1.242.68.in-addr.arpa" in {
        type master;
        file "db.1.242.68.in-addr.arpa";
};

zone "2.242.68.in-addr.arpa" in {
        type master;
        file "db.2.242.68.in-addr.arpa";
};

zone "3.242.68.in-addr.arpa" in {
        type master;
        file "db.3.242.68.in-addr.arpa";
};

...

zone "254.242.68.in-addr.arpa" in {
        type master;
        file "db.254.242.68.in-addr.arpa";
};

zone "255.242.68.in-addr.arpa" in {
        type master;
        file "db.255.242.68.in-addr.arpa";
};

Contents of db.255.242.68.in-addr.arpa:

@ IN SOA atlndns01.spcsdns.net. root.atlndns01.spcsdns.net. (
        2003121301
        10800
        3600
        604800
        86400 )

                        IN      NS      atlndns01.spcsdns.net.
                        IN      NS      chardns01.spcsdns.net.

0       IN      PTR     014-408-190.area7.spcsdns.net.
1       IN      PTR     014-408-191.area7.spcsdns.net.
2       IN      PTR     014-408-192.area7.spcsdns.net.
...
253     IN      PTR     014-408-443.area7.spcsdns.net.
254     IN      PTR     014-408-444.area7.spcsdns.net.
255     IN      PTR     014-408-445.area7.spcsdns.net.

Some errors that I see on an independent DNS server outside of my
network that occur in syslog when doing an audit via nslookup:

Jan  7 15:14:52 anomaly named[16698]: lame-servers: lame server
resolving '69.119.242.68.in-addr.arpa' (in '242.68.in-addr.arpa'?):
207.15.68.164#53
Jan  7 15:14:52 anomaly named[16698]: lame-servers: lame server
resolving '69.119.242.68.in-addr.arpa' (in '242.68.in-addr.arpa'?):
207.15.68.36#53

This tells me that 207.15.68.164 (osscdns01.spcsdns.net) and
207.15.68.36 (osscdns02.spcsdns.net) are not SOA for that particular
domain.  However per ARIN it is.  I'd like to set it up correctly,
however, and have a db.242.68.in-addr.arpa zone on those two servers
with NS records pointing to the servers that it's delegated to, although
that just did not work.  Here's an example of how I used to have it set
up.

On osscdns01/osscdns01

zone "242.68.in-addr.arpa" in {
   type master;
    file "db.242.68.in-addr.arpa";
};

@ IN SOA osscdns01.spcsdns.net. root.osscdns01.spcsdns.net. (
        2003121702
        10800
        3600
        604800
        86400 )

242.68.in-addr.arpa.    IN      NS      chardns01.spcsdns.net.
                        IN      NS      atlndns01.spcsdns.net.

And the zone files exist as they are today on chardns01 and atlndns01
broken up into class C zones.  I wanted to keep them in class Cs for
ease of administration, however if I have to combine it into one huge
file for the class B using $ORIGIN statements, then I will.  I'd like to
avoid that.  So the end all question is; how to I delegate a class B?
Thanks for reviewing my post and I send a preemptive thanks for any
replies.  

-Paul Pasika
913-227-5097
paulpasika at nmcc.sprintspectrum.com




More information about the bind-users mailing list