Well you can thank VeriSign:
If your site has stopped working, you might be affected by a recent change to .com, .net, and .edu domain names. This change from VeriSign® requires that the NS records for a domain name have associated A records.
Thanks for the heads up on this one. I've just blown 4 hours working this out.
Here's what you have to do via
Godaddy:
How do I fix it?
You need to log in to your control panel and modify the affected domain name's zone file, using the table below as an example.
To Modify or Add DNS Records in Plesk
- Log in to Plesk as an Admin.
- From the list of domains at the bottom of the page, click the domain name you want to work with.
- Under the Services group, click the DNS button.
- To add a DNS entry, select the type of record you want to create and click Add.
To Modify or Add DNS Records in Simple Control Panel
- Log in to Simple Control Panel.
- Click the DNS button on the main screen.
- Click the Edit icon (the pencil) to the right of the domain name you want to modify.
- Change the desired A and NS records and save the changes.
To Modify or Add DNS Records in cPanel
- Log in to cPanel at http://yourdomainnamehere.com/cpanel.
- In WHM, click DNS Functions, and then select Edit DNS Zone.
- Click the domain you want to modify then click Edit.
- Enter the new DNS information then click Save.
Assuming your domain name is coolexample.com and your IP address is 74.15.27.119, your zone file needs to have the following NS and A records to resolve properly:
Where ns1 and ns2.yournameserver.com are the nameservers your domain name is pointing to.
If you have an NS record without a corresponding A record, add the A record and make sure it points to the site's IP address.
Most importantly, and not very clear from the above:
ADD THE NS2.yournameserver.com A record in the DNS Settings of your Name Server NOT the domain (coolexample.com)
Posted via email from mfsmillie’s posterous
