Problem with glue records..

[Bob Vance]

Did you actually also have a zone file on your server for the
delegated zone?
Or are you just referring to the PTR records that were left in the zone
file after you delegated the sub-zone.

>I fixed it ...

By just removing the PTRs left in the zone?


>bind 8.2.3 refuses the zone with "no glue" errors.

First you had "extra" records that weren't glue -- now
you just have no glue, huh :)


Now, I'm far from an expert on DNS, but this is the way I understand it:

If I delegate a sub-domain:

$ORIGIN mydom.com.
   ...
sub  IN NS    ns.sub.mydom.com.

to a server *within* the sub-domain, how am I or anyone else going to
find its IP address, say, to handle a recursive request for a name in
that domain?

ns.sub.mydom.com. knows the IP address of ns.sub.mydom.com., since it's
the master for it, but nobody else does!!

My delegation is the only "jumping off point" to this delegated server.
So it's kind of a chicken-egg thing.

I just have to bite the bullet and code in a glue record for that
nameserver:

$ORIGIN mydom.com.
   ...
sub  IN NS    ns.sub.mydom.com.
ns.sub.mydom.com.  IN   A  1.2.3.4

This name really belongs in the delegated zone, "sub.mydom.com.", but it
is allowed here because we *need* it -- as glue.

Another record, say

foo.sub.mydom.com.  IN   A  1.2.3.7

would be non-glue and would be generate error.


-------------------------------------------------
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: Monday, February 05, 2001 12:07 PM
To: bind-users at isc.org
Subject: Re: Problem with glue records..


Yea, I was deligating part of my RR's to myself.  Dumb.  I fixed it and
it
works now.  It's strange that it worked with 8.2.2 but not with 8.2.3
but
there are alot of things that way.  ON another note, can a name have an
MX
but not an A record?  I don't see anything in the RFC's that say so but
bind 8.2.3 refuses the zone with "no glue" errors.  I don't see that an
A
record should be necessary for mx records.  I'd like to have

email.colorado.edu.	in 	mx	10	mx.colorado.edu.

even if email.colorado.edu doesn't exist.

						Robert Weber
						University of Colorado


--------

> Did you ever get this resolved ?
>
>
>
>
>
>
> -----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
> ----------
>
>
>

--------

----------
Resolved: by weberr Mon Feb  5 10:04:16 2001
----------