Here's what I notice.
I had the nameservers set to NS1, and NS2 in the TechInfo. So the client
gets that by default.
They are CNAMEs for the nameservers proper.
I went into ManageDomains for the registered domain,
In the [Manage Domains] interface, it had ns1 and ns2 showing as the
nameservers - but NO IP associated there with them ????
I changed the nameservers in the ManageDomains interface to the Actual
servers, not the CNAME, but the real name, and up popped the IP of the
nameservers. Which surely must make things easier to find right off.
The ManageDomains apparently isnt doig a lookup of the CNAME type name -
only the genuine nams for nameservers.?
Now to see if the offending nampe propogates correctly.!!! ( I also changed
my DNS db records of course...)
----- Original Message -----
From: "Marc Schneiders" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 30, 2000 1:18 PM
Subject: Re: [Q] Period from registration to traceroute success? US/CA to Oz
(fwd)
> My server cannot find aussiebackpacking.com. My earlier mail I sent
> only to the list. As I do this one. I have had similar porblems with a
> domain in .NZ some time back. I have no idea. This time it cannot be
> resolver timeout due to bad connection.
>
> I killed named completely and restarted it, still no
> aussiebackpacking.com. nslookup and dig suggest your nameservers are
> working. Gtld-servers.net also know about your domain. I am lost. I
> did get twice a 'connection refused' message in nslookup. I am no DNS
> guru. So anyone?
>
> Oh, yes, I do get the IP I found through nslookup. It gives a webpage
> saying 'Quantum Radio'. And when I try to register
> aussiebackpacking.com though the site, it says, it is already
> gone. So all that is fine. It must be DNS then.
>
> --
> Marc Schneiders (rest in header)
>
>
>
> Hmmmm, well this is ver ystrange. I registered a domain on the 26th in the
> COM zone. It appears in the whois ok, but a traceroute from just about
> anywhere in the world - even in Australia - fails, "unknown host". Yet it
is
> already the 30th now - 4 days.
> There are other domains registered and all working fine after only a short
> time, so I can't understand why this one is sticking...
>
>
>
