Search Again:

Re: Domain name problem

From: Global Homes Webmaster
Date: Thursday, May 18, 2000
Time: 10:34:08 am

On 05/18/00 at 12:16, Mia's Virtual Post Office wrote:

> I posted this a few days ago, and did not see a response, but I get a lot
> of mail so may have missed it. I did not see anything in the archives
> though.
>
> thanx,
>
> <SNIP>
>
> We have a major problem with a domain we host. It happened yesterday to
> the best of our knowledge. The domain is called daralfunoon.com
>
> The customer notified us yestereday that there site is unreachable via
> the web. They have another domain here called dar-al-funoon.com which
> works fine. Here is the problem:
>
> Both the customer as well as queries from netcraft, and via DNS Expert
> say that the domain is not registered anywhere. Yet a whois confirms
> that it is registered, and is paid for, and has not expired. Also, an
> nslookup inside our network confirms it works. Retrieveing the site via
> a browser on our network works. However, outside our network the domain
> is not working. We have not changed anything at all. This domain has
> been working happily since 15-Feb-2000 when we set it up.
>
> I have re-created the zone file, updated my primary and secondary, etc..
> To no avail the domain will not seem to be recognized outside our
> network. We have around 2000 or so domains hosted in our primary dns as
> we speak and all of them appear to work, except this one.
>
> any ideas? could this be a NSOL problem?

Yes, I'd say it looks like a NetSol problem. NetSol's Whois lists the domain,
along with your name servers, but the root servers do not have NS records for
daralfunoon.com. If the root servers don't delegate it anywhere, then no one
on the internet at large will be able to find it. It works from your internal
network because, presumably, your local computers are configured to use your
name server(s) for resolution. Since your name servers have authoritative data
for daralfunoon.com., they can resolve it. Because the root servers don't have
NS records for it, name servers outside your network can't know that your
servers have authoritative data for it, so they can't resolve it. It's a
Network Solutions problem because they are responsible for adding domains
registered through them to the root servers.

Christopher Bort



Messages In This Thread:



Return to Digital Point Solutions' Home Page