I have one .INFO domain name:

ezc.info

I am using my own dedicated server as the name server. However, when I enter the domain name into my browser address bar (after not having visited the domain for a while), it seems to take for ever (over a minute!) for the name to get resolved and for me to be returned the web page that it should be pointing to (its HTTP Authorisation restricted at the mo folks).

I don't know where the problem is. Whether it's my ISP (bigpond.net - AU), or the fault of whoever it is who hosts the INFO. TLD whois database, or what!

Can anyone offer any information that may help me understand why it takes so long for the domain name to resolve to my server?

Thanks :)

Originally posted by freakysid
I have one .INFO domain name:

ezc.info

I am using my own dedicated server as the name server. However, when I enter the domain name into my browser address bar (after not having visited the domain for a while), it seems to take for ever (over a minute!) for the name to get resolved and for me to be returned the web page that it should be pointing to (its HTTP Authorisation restricted at the mo folks).

I don't know where the problem is. Whether it's my ISP (bigpond.net - AU), or the fault of whoever it is who hosts the INFO. TLD whois database, or what!

Can anyone offer any information that may help me understand why it takes so long for the domain name to resolve to my server?

Thanks :)

Shouldnt really be a TLD problem, seems more like a client side issue to me, do other domains on the same machine resolve without a problem?

No problem accessing .COM .NET .ORG domains from my client (through bigpond.net) - all resolve quickly. Maybe its something to do with my ISP bigpond.net's DNS because when I enter EZC.INFO into samspade.org's box of magic tricks - I get served back the whois record, trace route info, etc from the samspade.org site faster than it takes for ISP to resolve the domain name. So you think it might just be a problem with my ISP?

Takes ages for me as well. The first time at least.

My best guess would be it has something to do with your nameservers. I see you use ns1.neaturl.com and ns2.neaturl.com
Also when I look up ezc.info I am taken to neaturl.com. I assume this is on purpose.

Check if your ns1.neaturl.com is configured in the correct way for the domainname ezc.info
It almost looks like ns1.neaturl.com can't find ezc.info and after the specified time turns over the task to ns2.neaturl.com who CAN find it.

That would explain the delay. Just a theory.

Thanks for your reply. I am cheating in that ns1.neaturl.com 64.156.2.192 and ns2.neaturl.com 65.56.0.15 are the same server.

However, if the problem is with my DNS file for the domain name - then blast if I can find what I have done wrong! Here is the file ezc.info.hosts

$ttl 38400
ezc.info. IN SOA dylan.neaturl.com. hostmaster.neaturl.com. (
1003063895
10800
3600
432000
38400 )
ezc.info. IN NS dylan.neaturl.com.
ezc.info. IN A 65.56.0.40
*.ezc.info. IN A 65.56.0.40
ezc.info. IN MX 10 mail.neaturl.com.


ns1.neaturl.com and ns2.neaturl.com have both been registered as name servers with register.com who are the registrar for the domain name neaturl.com. Is there anything else I need to do because this is an .info domain name? Is there someone else I should be registering those name server addresses with?

And, yes, the domain should redirect to neaturl.com If you type foobar.ezc.info into your browser window you will see why ;) (eventually - when the blasted domain name gets resolved!).

sigh!

Thanks for your help :)

<<edit>>
woops! I did have one error. In the SOA where it now says hostmaster.neaturl.com. before it said just hostmaster. But that wouldn't be a problem? Or would it? :eek: