View Full Version : Server not found persists

07-21-2004, 05:00 PM
Okay, I've searched the forum archives and followed the instructions on the support pages for the solution to this problem and now, I'm asking for help.

I recently purchased a new domain, one that (for the time being) I want to be pointed at my existing domain on Westhost. The registrar was provided the DNS servers information and a quick WHOIS search does verify that they are set correctly. I've added the domain in my control panel and waited the requisite 72 hours (plus an additional 24), however my new domain name still will not access the original site. I get "server not found" errors.

I've done this before, but that was in the days of WH1 and there was no problem. I already have two other domains pointing at the same (original) domain and they still work perfectly. So I have to assume that I've missed something incredibly simple, but I'm darned if I can figure out what it is.

Short version (too late!) is, I have mydomain.net, my primary account, with myotherdomain.net and mythirddomain.org both accessing and displaying mydomain.net when someone types in one of those addresses instead. What I can't seem to make work is mynewestdomain.org to do the same. Since my intention is to eventually have mynewestdomain.org become the primary, I really need this to work as soon as possible.

Thanks for any assistance.

07-21-2004, 05:21 PM
Is the new domain in manager pointed to the default?

If yes - then I remember when I added my second domain - it didn't work after 72 hours so I called westhost support - they worked some magic and voila!


07-22-2004, 01:46 AM
Well, I used the domain manager to add the new one and left the default setting as it was, so I have to assume that it's still pointed to the default.

I was kind of hoping to avoid calling Westhost support. Not that they haven't been very kind and helpful when I've had to call in the past, but I'm one of those people that prefer not to ask others to do what I should be able to.

I guess I may have to anyway. Just in case someone from Westhost does read these forums though, here are my specific domains:

drwp.net (this is the original)
dachshundnetwork.net (this works properly, displaying drwp.net)
dachshundnetwork.org (same with this domain)
dachshund-rescue.org (this is the one I can't get to work - it should also display drwp.net)

Maybe I'll get lucky and by the time I get home from work today, someone from Westhost will have seen this thread and have shown mercy on me. If not, I guess I'll have to call.


07-22-2004, 02:50 AM
When you did the installation through the manager it made the entries in to the west-datacenter.net name servers. You have your domain pointing to the old ns.westhost.net name servers.

Change the DNS entry to point to ns1/ns2.west-datacenter.net and it should work OK.

07-22-2004, 12:39 PM
All of the domains point to the ns.westhost.net name servers. Why would the new domain be the only non-functional one of the group?

Does this mean I also need to contact the registrars for the other 3 domains as well? (4 domains, 4 registrars, compliments of an over-enthusiastic volunteer)


07-22-2004, 02:10 PM
All of the domains point to ns.westhost.net servers, that is true, but only three of the domains are registered on ns.westhost.net name servers, the other one, the one that is missing, is listed on west-datacenter.net servers.

dachshundnetwork.net doesn't seem to be a registrared name...???

$ dig drwp.net
;drwp.net. IN A
drwp.net. 10767 IN A
drwp.net. 10767 IN NS ns1.west-datacenter.net.
drwp.net. 10767 IN NS ns2.west-datacenter.net.

$ dig dachshundnetwork.org
;dachshundnetwork.org. IN A
dachshundnetwork.org. 10800 IN A
dachshundnetwork.org. 10800 IN NS ns1.west-datacenter.net.
dachshundnetwork.org. 10800 IN NS ns2.west-datacenter.net.


$ dig dachshund-rescue.org
;dachshund-rescue.org. IN A

which means no entry found in the DNS system

$ dig @ns.westhost.net dachshund-rescue.org
;dachshund-rescue.org. IN A

and, confusingly:

$ dig @ns1.west-datacenter.net dachshund-rescue.org
;dachshund-rescue.org. IN A
dachshund-rescue.org. 10800 IN A
dachshund-rescue.org. 10800 IN NS ns2.west-datacenter.net.
dachshund-rescue.org. 10800 IN NS ns1.west-datacenter.net.

while doing a whois on dachshund-rescue.org finds the name servers set to point to ns.westhost.net....

I would suggest getting all your domains pointing to ns1/ns2.west-datacenter.net.
These are the standard, recommended name servers for westhost.

That should have it all sorted out....


WestHost - MMellor
07-23-2004, 11:25 AM
Hello Frisky,

I just pulled that up to start working on it and looks like it is working. http://www.dachshund-rescue.org is pulling up http://www.drwp.net Is that what you wanted to happen or did I miss something? Keep us posted on your progress with this.

07-23-2004, 01:31 PM
It would appear that Jalal had the missing piece to the puzzle. Not being aware that the name servers had been changed, and with the current domain still being pointed at the old name servers, I foolishly assumed that the original name servers were the ones I needed to give to the registrar.

With all of my registered domains now pointing at the new name servers, everything is working exactly how I wanted it to. I knew it had to be something incredibly simple and easily overlooked that was my problem. Thanks, Jalal. You too, Westhost.

Just as a casual observation, whenever someone adds a domain in the control panel, it might be a good idea to have a dialog box confirming which name servers need to be given to the registrar. That way there's no question for those of us who know just enough to be dangerous.


WestHost - MMellor
07-23-2004, 02:05 PM
Hello Frisky,

That is a good point and I will pass that on. For future reference any new domain that you are adding will always have these as the name servers:


I'm glad that you got that working. Let us know if there is anything else you need help with.