Problem with glue records..

[Bob Vance]

Once you delegate the subzone to the other server(s), then you must
get rid of the data for those sub-zones that used to be in your zone:

OLD:
-----
$ORIGIN  138.128.in-addr.arpa.
   ...
;; subnet 20
103.20    IN   PTR    blah.cs.colorado.edu.
104.20    IN   PTR    blow.cs.colorado.edu.
   ...

NEW (delegated):
----------------
$ORIGIN  138.128.in-addr.arpa.
   ...
;; subnet 20 - delegated
20      IN  NS   ns1.cs.colorado.edu.
20      IN  NS   foons.colorado.edu.
;;;;103.20    IN   PTR    blah.cs.colorado.edu.
;;;;104.20    IN   PTR    blow.cs.colorado.edu.
   ...

If you *don't* delete the 103.20 record, it will be

103.20.138.128.in-addr.arpa.  which is in the zone you just delegated!!
(and is not a glue record :)

-------------------------------------------------
Tks        | <mailto:BVance at sbm.com>
BV         | <mailto:BobVance at alumni.caltech.edu>
Sr. Technical Consultant,  SBM, A Gates/Arrow Co.
Vox 770-623-3430           11455 Lakefield Dr.
Fax 770-623-3429           Duluth, GA 30097-1511
=================================================





-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Robert Weber
Sent: Friday, February 02, 2001 7:58 PM
To: bind-users at isc.org
Subject: Re: Problem with glue records..


Ok, I did some more digging and it appears to be more of a problem with
how
I do subnets and reverse dns.  All my subnets complain about non-glue's,
not just cs.  Here's part of my config:

named.conf:

zone "colorado.edu" {
        type master;
        file "named.colorado.edu";
	check-names warn;
                };
};

zone "138.128.in-addr.arpa" {
        type master;
        file "named.colorado.edu.rev";
        check-names warn;
};
zone "resnet.colorado.edu" {
        type master;
        file "named.resnet";
        check-names warn;
};

and from named.colorado.edu.rev:

; resnet subnets...
20      in      ns      boulder.colorado.edu.
        in      ns      cujo.colorado.edu.


but with all this:

Feb  2 16:46:07 boulder named[5397]: zone: 138.128.in-addr.arpa/IN:
non-glue record below bottom of zone: 103.20.138.128.in-addr.arpa/PTR


Still failing.  Does this mean I need to declare 20.138.128.in-addr
zones
in order for this to work again?  I have 40 of these subnets.  but if
it's
the only way then I'll start coding.

						Robert



--------

>
>
> Problem:  My nameserver is authoritative for colorado.edu, and our B/C
> classes which inculde 128.138.  I am not autoriative for
cs.colorado.edu,
> but they also exist in 128.138 so I am authoritative for their PTR
records.
> now that I moved to 8.2.3-REL my reverse zone is rejected due to:
>
> Feb  2 15:23:42 boulder named[5397]: zone: 138.128.in-addr.arpa/IN:
> non-glue record below bottom of zone: 1.250.138.128.in-addr.arpa/PTR
>
> Errors for every host within cs.colorado.edu. Which leads to:
>
> Feb  2 15:23:42 boulder named[5397]: master zone
"138.128.in-addr.arpa"
> (IN) rejected due to errors (serial 200102023)
>
> Campus politics prevent me from taking cs.colorado.edu back, what can
I do
> to configure bind 8.2.3 so that it either ignores these errors or
works.
> This did work with 8.2.2
>
>
> 						Robert Weber
> 						University of Colorado
>
>
>
>

--------

----------
Status: by weberr Fri Feb  2 17:33:14 2001
----------