Mystery Name Server HEEELLLP!!!

Fri Apr 19 01:04:10 UTC 2002

	I'm going to guess that this link will help you out.
http://rightnow.godaddy.com/cgi-bin/rightnow.cfg/php/enduser/std_adp.php?p_sid=EN8KD-cg&p_lva=&p_refno=020205-000468&p_created=1012944433&p_sp=cF9ncmlkc29ydD0mcF9yb3dfY250PTExMiZwX3NlYXJjaF90ZXh0PW5hbWUgc2VydmVyJnBfc2VhcmNoX3R5cGU9MyZwX3Byb2RfbHZsMT1_YW55fiZwX3Byb2RfbHZsMj1_YW55fiZwX3NvcnRfYnk9ZGZsdCZwX3BhZ2U9MQ**&p_li= 

They explain how to register a name server on their site, this is most
likely where www.employment-lawyers.net has been set up.

If the above link doesn't work, you can always do what I did - go to
http://registrar.godaddy.com click on the customer support link ->
online support -> search for your answer here -> put in "name server"
into the text search field, and click on the first link ( Updated - How
do I register a name server with Go Daddy? )
Kurt Heston wrote:
> Pete,
> 
> Thanks for the long explanation, things are getting clearer.  Just so you
> know the problem is not just in my being thick in the head (although that
> has been an issue in the past I'll admit) I'll include my correspondence
> with GoDaddy (more of my message follows):
> 
> <begin messages with GoDaddy>
> *****************************************************************
> ---- 04/17/2002 08:25 AM ---------------------------------------------
> I've had some trouble with www.employment-lawyers.net resolving to the wrong
> IP address for some time now. There is a name server record shown by whois
> at the internic site that says www.employment-lawyers.net is a name server
> at 63.193.248.196 and that this entry is a godaddy entry??? I've made no
> such entry with you, how did it get there?
> 
> Your help on this would be appreciated, thanks.
> --Kurt
> ----------------------------------------------------------------------------
> -----------------------
> At 04/17/2002 11:48 AM we wrote - Kurt,
> I can not find any evidence of a DNS server being registered with your
> domain name. I can see that your current DNS settings are set to NS1.HN.ORG
> and AUX1.HN.ORG. If your name will not resolve it has to be an issue with
> the listed DNS servers. I would recommend you contact your hosting service
> provider, or DNS provider.
> 
> Please let us know if there is anything else we can help you with. Visit our
> web forum for information that may answer some of your questions at:
> 
> Jason K.
> Go Daddy Software
> 
> ----------------------------------------------------------------------------
> -----------------------
> ---- 04/17/2002 12:06 PM ----------------------------------------------
> Jason,
> 
> If you go to internic.com and do a whois on www.employment-lawyers.net,
> you'll see that it says godaddy has a name server entry for 63.193.248.196.
> There is no such entry at hn.org. It must be at godaddy, if it's not, where
> is it? Can you help me find it pleeeease?
> 
> Thanks for the help,
> Kurt
> ----------------------------------------------------------------------------
> -----------------------
> Dear Sir or Madame,
> 
> Go Daddy does not have control of your DNS so there is nothing that we can
> do to help. You will need to contact hn.org to resolve your DNS issues.
> 
> 63.193.248.196 is not a Go Daddy IP address. I did a lookup on it and here's
> what was returned.
> 
> Pac Bell Internet Services (NETBLK-PBI-NET-7) PBI-NET-7
> 63.192.0.0 - 63.207.255.255
> ADSL BASIC-rback8-snfc21 (NETBLK-SBCIS990913-43) SBCIS990913-43
> 63.193.248.0 - 63.193.251.255
> 
> Dan Snyder
> Go Daddy - Tech Support
> 
> ----------------------------------------------------------------------------
> -----------------------
> ---- 04/18/2002 09:25 AM ----------------------------------------------
> Dan,
> 
> It's been recommended to me that I enlist the help of my registrar in
> getting rid of a "bad glue" record for one of my domain names registered
> with godaddy. You can see the entry with this dig command:
> 
> 'dig @a.gtld-servers.net www.employment-lawyers.net a'
> 
> The record I'm hoping to get rid of is the one referencing 63.193.248.196.
> Would please help me get erradicate it? I've been battling this problem on
> and off for over a year now.
> 
> Thanks,
> Kurt
> ----------------------------------------------------------------------------
> -----------------------
> At 04/18/2002 03:46 PM we wrote -
> 
> Dear Sir or Madame,
> 
> I'm sorry, but as I said last night, Go Daddy does not have control of your
> DNS so there is nothing that we can do to help. You will need to contact the
> company that currently has control of your DNS, hn.org for help resolving
> this issue.
> 
> Dan Snyder
> Go Daddy - Tech Support
> *****************************************************************
> <end of messages with GoDaddy>
> 
> Where have I gone wrong here, was I bananas to think my registrar would help
> me with this?  GoDaddy doesn't seem interested, are they my only recourse?
> This bad entry existed before I transferred the name to GoDaddy, how do I
> get it removed if I don't even know who entered it and does it matter
> (Cydian, my first and only other registrar told me the same thing GoDaddy is
> telling me)?  So what gives, am I just hosed?  Should I let my registration
> lapse and forget I ever owned this domain name?
> 
> They want me to talk to HN.  Well, I make the entries at HN via a
> self-service portal and haven't ever made an entry like the problematic one.
> They have provided me with an awesome free service, one that is working
> flawlessly for my other 6 domain names.  So, what can hn.org do for me?  If
> their server is lower in the search tree than the bad entry, no entry made
> by them will make any difference, correct?
> 
> I'm not sure this is one of those cases where the problem is an idiot at the
> keyboard, well, at least not this keyboard.  I think I have a genuine, not
> easily solved, thoroughly confusing issue here, one that has plagued me for
> over a year.
> 
> Your help is appreciated.  If I'm not able to determine the solution to this
> issue with your help or that of another DNS guru, I'm going to label this an
> unsolvable mystery and will be throwing in the towel.
> 
> --Kurt
> 
> 
> 
> "Pete Ehlke" <pde at ehlke.net> wrote in message
> news:a9nerd$nn6 at pub3.rc.vix.com...
> 
>>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
>>
> 
> 
> 