Thread: Site doesn't exist?

Been trying to submit two of my newest sites for a couple of days to Yahoo now @ https://siteexplorer.search.yahoo.com and it keeps on telling me the URLs don't exist.

If it was a brand spanking new domain, I would understand. One is 3 months old another is 3 weeks old. One of them is even in Yahoo's index.. What gives?

Any ideas?

Hey Danny ...
Do you have any quality IBLs going to the sites? For the site that has being listed on the index, I suspect their may be some sort of synchronization issue between the index and siteexplorer. Just grabbing at straws here.

Not yet, Frank except for a few forum sig links. I'm really just kicking the sites off and wanted to give site explorer the feed to grab.

I've already gotten an API to send a sitemap to Yahoo and the sitemap script reports no problems with the ping.

My sound thought was maybe their is an issue because I have API keys for the domain but they were aquired under the same Yahoo ID so it shouldn't be an authenication problem.

Danny ... try to get at least 1 decent / relevant IBL from a fairly busy site. Also check your page headers and robots.txt file to make sure there is nothing there causing the problems.

Does this happen to be the new NY chat site? I always get "page unfound" in your link on here and I was hoping to check it out.

Originally Posted by Kaos

Does this happen to be the new NY chat site? I always get "page unfound" in your link on here and I was hoping to check it out.

Yes, that's one of them. Really? I moved it a couple of times but I see it fine. I'll check through a couple of proxies.

If you could do me a favor, ran a traceroute to the domain:

Start, Run type: cmd

In the box that comes up type: tracert discussny.com.

Paste the output here, please.

Unable to resolve target system name discussny.com - looks like DNS issues

Thanks, Frank I just dropped my hosts support a message. I tried browsing the site through proxies and am seeing the error.

Funny, it seems to be all of the domains I moved over from the second VPS.

Sorry for the DP: I figure someone else might come across this problem.

What seems to of happened is when I first moved the sites to the new VPS, I took the lazy way out and swapped out the name server IPs trying to save myself sometime updating the name servers for all my domains. Essentially what I did was went to GoDaddy and changed the IPs for the nameservers that were pointing to the old server.

Then I got a brain storm and decided I wanted to use bigdan.us for name servers so I went through and changed all my DNS + Added the IP for ns1&ns2.bigdan.us at GoDaddy.

cPanel went back and updated itself from the DNS cache and modified the name server IPs to my old domain for those IPs since the cache had not refreshed itself yet.

That was the problem basically cPanel had the wrong name servers were pointing to those IPs.

Solution:

I turned off the auto-refresh and allowed multiple name servers to use the same IP.

Problem:

cPanel still wouldn't let me delete the old name servers and add the new ones, citing the name servers still had an entry at an ICANN registrar. I figured out that GoDaddy didn't delete the old name server bind as I requested thus causing the DNS servers to be confused.

Solution:

Edit /etc/namserverips, change the entry to those IPs. Reboot the server.

So far it's stuck, if those of you who couldn't get to the site yesterday would give it a shot in an hour or two. I'd really appreciate it.

In short,

Don't be sloppy and take shortcuts when setting up name servers. Lesson learned for the big guy.

Darn, I love shortcuts :-) I'll check it out for you in a little while.

Danny the moral of the story is - Don't take short cuts ... not even with your GF