Mystery Name Server HEEELLLP!!!

Pete Ehlke pde at ehlke.net
Thu Apr 18 21:40:20 UTC 2002


On Thu, Apr 18, 2002 at 04:13:33PM +0000, Kurt Heston wrote:
> 
> I am the one in control of the entries at hn.org and I've done what you've
> suggested (it won't fix my problem because none of the entries referenced
> the baqd ip).  Did you notice however, that even though those entries
> existed, www.employment-lawyers.net was still resolving to 63.193.248.196?
> This is the issue I'm trying to fix.  Is it possible that there's another
> server out there besides the ones at hn.org that could have a very old
> record cached?  If so, how would I go about finding it?
> 

Look, several people have told you several times apiece. There is a host
record, sometimes called a glue record, for www.employment-lawyers.net.
This record is held at the gtld server level, and not on your name
servers. Nothing you do on your servers will affect it. You need to go
to your registrar (godaddy.com) to either change its address or have it
deleted.

It seems that you may not understand the concept of glue records. If
someone registers, say, fubar.com, and they want ns1.fubar.com and
ns2.fubar.com to be the registered name servers for that zone, then
there is a chicken and egg effect. In order to discover addresses in the
fubar.com zone, one has to know the addresses of ns1.fubar.com and
ns2.fubar.com. But in order to get those addresses... See where this
leads? 

This problem is solved by creating what is called a host record. A host
record, or glue, is simply an A record that is held by servers at some
level above the zone they exist in in the DNS heirarchy. That way, when
the gtld servers tell you that in order to resolve www.fubar.com you
need to ask ns1.fubar.com or ns2.fubar.com, they *also* tell you the
addresses of those servers.

At some point in the past, you or someone else associated with
employment-lawyers.net registered a host record for
www.employment-lawyers.net. Since that record exists farther up the food
chain than the records returned by your servers, most clients will see
*it* instead of your records.

This is not caused by any sort of configuration error on your servers,
nor is it caused by some weird serial number format, nor is it caused by
the phase of the moon or Bill Gates. 

Several people have told you what to do- contact godaddy.com and have
the host record modified or deleted.

-Pete
-- 
"religious fanatics are not part of my desired user base." 
- djb at cr.yp.to


More information about the bind-users mailing list