Checking a Site's DNS & Getting Online

Hey there,
I was wondering if someone could help me with a problem I am having. I have registered a domain name at yahoo, and changed the nameservers, but keep getting a 'site not found' from my local ISP.

Can anyone help?

Thanks.

 

Clean your local dns cache. Try changing your dns to www.opendns.com

 

Well, it's an ISP, I don't know if I could clean the cache on that? (sorry, a little confused)

Update: I ran "ipconfig /flushdns" but no dice.

Thanks anyway.

 

Like is there a tool maybe to check to see if everything is set up ok (and ready to go)? and what do I need to look for? I don't want to keep waiting if something is not set up right.

Thanks in advance.

Lance

 

http://dnsstuff.com/ works well to check your DNS config.

I would have a look for you but you don't give the domain name in questions.

Sure it doesn't just need longer for the changes to take affect, they can take 48hrs.

 

hey thanks Tolra, yeah that's what I was thinking, but I was wonder if there was something I could check to just make sure it's a time thing and that everything is ok. What should I check for on the dnsstuff.com tool?

By the way, the domain is www.boatingemporium.com and the hosting service said everything was fine when I added it a day ago, but maybe it is a problem with them.

Thanks!

 

Just pop in the domain name in the DNS report and look for errors and warnings, also make sure it shows your name servers.

 

Ran the check on the site, (the one I posted above) and got 4 errors

 

Neither of the 2 nameservers you have listed for the domain will answer queries on the domain that is they don't know what the domain is.

You have these 2 set:

ns53.domaincontrol.com. [216.69.185.27] [TTL=172800] [US]
ns54.domaincontrol.com. [208.109.255.27] [TTL=172800] [US]

If they are not correct then you need to update the nameserver records of the domain, if they are correct then you need to talk to your web host as for some reason it looks like the zone records were not created.

 

Ok, thanks so much, so it was a problem with the host? That's what I was thinking.

Thanks again.

 

If those 2 names servers are correct for the host then yes it's a problem with the host as neither knows your domain.

 

ok thanks, so let me get this right, I update the nameservers in the domain hosting control panel, then in the hosting control panel, add the domain, right?

Thanks!

 

Should I worry about the A names or not?

 

Yes, however the thing is as far as I can see the name servers you have listed don't know about the domain name. You need to throw a ticket at your host so they can sort it out for you, should be a quick fix.

 

Thanks Tolra, you've been a big help. I've repped you by the way.

 

Everything is fixed now, it was a problem with the host. Thanks to all who helped! You can close this thread now.

 

Actually, I don't think it is fixed as I just checked your domain and get errors:

WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).

66.197.153.229 returns 0 answers (may be a referral)
64.235.48.196 returns 0 answers (may be a referral)

Code (markup):

ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
66.197.153.229
64.235.48.196

Code (markup):

ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns01.000webhost.com.
ns02.000webhost.com.

Code (markup):

No valid SOA record came back:
is not boatingemporium.com.

Code (markup):

Also any manual looks ups for the domain against those nameservers fails.

Therefore it looks like those 2 nameservers still don't know about your domain and therefore your site is still not functional, poor very poor.

 

Oh, its ok now, I ended up changing them, probably why you were seeing the errors, but it was a problem with the host at first. Thanks so much to all who helped.