This is to notify members that Godaddy has a known issue with their DNS forwarding that has been going on for at least 12 months.
The issue involves forwarded domains be resolved to Godaddy parked pages with all revenue collected by Godaddy. The problem is widespread and random.
Here's an example:
A registrant has 100 domains parked at Sedo. The registrant (account holder) then decides to use Godaddy forwarding to redirect the domains to a website instead of using Sedo. The registrant properly modifies the DNS within Godaddy's Domain Manager for each domain to use Godaddy Parked Servers and then forwards the domains.
Results: Some of the domains get forwarded, but the vast majority wind up resolving to Godaddy parked pages. I'm not saying this is intentional, but Godaddy has been aware of this issue for at least 14 months and it has not been resolved.
Note: The only way to correct this problem, is to manually configure each domain to use an A Record of 64.202.189.170 (GD forwarding servers). And sometimes this too does not resolve the issue.
Just thought I'd offer a heads up to those that could be affected by this very strange and ongoing problem.
The issue involves forwarded domains be resolved to Godaddy parked pages with all revenue collected by Godaddy. The problem is widespread and random.
Here's an example:
A registrant has 100 domains parked at Sedo. The registrant (account holder) then decides to use Godaddy forwarding to redirect the domains to a website instead of using Sedo. The registrant properly modifies the DNS within Godaddy's Domain Manager for each domain to use Godaddy Parked Servers and then forwards the domains.
Results: Some of the domains get forwarded, but the vast majority wind up resolving to Godaddy parked pages. I'm not saying this is intentional, but Godaddy has been aware of this issue for at least 14 months and it has not been resolved.
Note: The only way to correct this problem, is to manually configure each domain to use an A Record of 64.202.189.170 (GD forwarding servers). And sometimes this too does not resolve the issue.
Just thought I'd offer a heads up to those that could be affected by this very strange and ongoing problem.
Last edited:




