Help with delegation

/dev/rob0 rob0 at
Sat Jun 11 01:22:12 UTC 2005

Michael Barber wrote:
> I am having a problem researching a domain delegation issue.  Thanking in
> advance for any help.

Welcome you are in advance of my attempt. :)

> I'm trying to delegate the entire * to a secondary
> location which will/should be running dns as will be the master? The name does not matter to DNS, 
although it may be an issue with the service provider (Zoneedit, for 
example, wants your NS records to point to $

> Here's my zone file.  I removed the glue record because it was logging an
> ignored message in my logs and was not mirring the glue record to the slave.

Glue is only when the NS name is in your zone. You could put the NS 
records in your zone. You would then need the glue in the parent domain. 
For second-level domains this is normally done at/by the registrar, but 
in your case it would be done by those who control 
(Appears to be you.)

> One of the hosts under this domain is  When
> I do a lookup at, I get this
> [snip]
> Searching for A record at
> []: Reports that no A records exist. [took 87 ms]
> Answer:
> No A records exist for [Neg TTL=3600
> seconds]

I get the same thing, albeit from the NS servers you mentioned.

> I have no direct control over the * zone.  Its being run
> by someone else. 
> Its not working....Is it possible to tell why or what I need to do to fix
> this?  
> Why does report that is authoritative?

When did you try it? Maybe NS and glue records at the parent domain 
weren't updated yet?

$ host -t ns name server name server
$ host
Host not found: 3(NXDOMAIN)

     1. Must have not waited long enough for propagation of records at NS servers.
     2. There IS no "A" record for

$ host
Using domain server:
Aliases: has address

One hour is an abnormally long time to cache NXDOMAIN results.
     mail to this address is discarded unless "/dev/rob0"
     or "not-spam" is in Subject: header

More information about the bind-users mailing list