Well, this has gone on for a week now and no one has any idea why. We recently took control of all our Domain Names from EasyDNS so we can run them in-house on our new Cobalt as we setup our new hosting department. I setup the NameServers with our Registrar and setup all the DNS info on the Cobalt. We currently have NS1 and NS2, IPs of .122 and .123. .122 was our old webserver address (now the cobalt) so all our website's address didn't change when we went from Easydns to our cobalt, and the .123 IP is currently our old Email server that we can't take offline yet because some customers are still using it. We can't turn it off until we get the websites to come up off the main server. This is the problem, for some reason, none of the websites show up and if I ping the domain name, it replies from our email server (.123, aka, NS2). So somehow, all of the requests get passed directly to the secondary name server either because the cobalt isn't replying or for some reason, the root servers are propigating the wrong IP. Even telling the email server to forward requests to the cobalt fails.
What's odd is that the office network has no problem finding the cobalt (aka NS1) and bringing up the websites, and after initially setting everything up and waiting 24 hours, it all worked fine, then started changing every evening, and now doesn't work at all. I didnt make any changes after initial setup. I even took the cobalt off-line and setup our old win2k webserver with the right DNS info and it still wont propagate or reply to domain requests from outside the office network. This has now put a kink in our timeschedule and no one seems to have an answer. The only thing I can think of is because we are currently on a business DSL, our providers nameservers are causing a problem, but inquries to them say its our problem. Did I miss a setting somewhere? Anyone else has this problem?
