More Technical Problems, PLEASE Read if You Forward Domains at Go Daddy
*
I suspect that last week's (7/18) crash has caused some other problems, and I just want to make you aware of them because GD will NOT help you because they don't want to admit that the problem went deeper than they are telling us.
A little background: when you forward your domains to another site, you'll see a little box that says, "Checking this box will update servers and DNS to support this change" (or something to this effect). The default is a check mark in the box, so I always left it. Always, the forwarding took place place almost immediately--most of the time, anyway, maybe a few hours later.
Well, I began noticing that my domains were NOT forwarding properly, and these were ones (seven domains) I was working with around the time of the crash.
You may want to check the domains you forwarded on July 18-20 to make sure they are resolving to your target page.
So, evidently, during and after the crash, the nameserver and DNS settings were NOT being changed to support any forwarding changes (though no one will admit it). These were mostly auction domains, but one was a actually a hand reg, which puzzles me....
If your domains are not resolving properly, support won't help you (even though it was their issue), but here's how you can make the change manually (This involves changing an IP number):
Log in to your Account Manager.
Next to Domains, click Launch.
From the DNS tab, select DNS Manager. The DNS Dashboard displays.
In the Domain list, for the domain name you want to update, click Edit Zone. The Zone File Editor displays.
In the A Host section, click the @ record.
For Points to, type 50.63.202.1 [Evidently, this is one, among many, of GD's forwarding IP's.]
Click Save Zone File, and then click OK.
And you're very welcome.
If your forwarding is working, you do NOT need to need to do anything. This crash did not affect everyone.
*