Could that just be because the propagation for ns1.tdnameservers.com 
hasn't really happened yet? Am I just being impatient?

	-- jon

Jeremy C. Reed wrote:
>> On my local machine, if I do an nslookup on blah.huggabear.com, it resolves
>> correctly to 69.55.220.101.
> ...
>> How does one go about trying to track that down? I'm not sure how to
>> systematically work through it...
> 
> The two responsible nameservers both timeout when I test.
> 
> Here are the commands I ran:
> 
>   dig blah.huggabear.com @b.root-servers.net  NS
> 
>   dig blah.huggabear.com @G.GTLD-SERVERS.NET.  NS
> 
>   dig blah.huggabear.com @ns1.tdnameservers.com. NS
> 
>   dig blah.huggabear.com @ns2.tdnameservers.com.
>   
>   dig blah.huggabear.com @ns1.tdnameservers.com.
> 
>  Jeremy C. Reed
> 
> echo ':6DB6=88>?;@69876tA=AC8BB5tA6487><' | tr '4-F' 'wu rofIn.lkigemca'
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> 
> .
> 
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change  you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss