OVH域名切换GoDaddy DNS服务器失败求助：状态异常且服务器无响应

Let’s break down what’s happening here and walk through actionable steps to get your domain back on track:

1. Double-Check GoDaddy’s DNS Setup for the Problematic Domain #

Since one of your OVH domains works fine with the same GoDaddy DNS setup, the issue likely lies in a configuration mismatch for the problematic one:

• Log into your GoDaddy account and navigate to the DNS Manager. Search for the inactive domain—does it show up here? If not, you may need to manually add it to GoDaddy’s DNS system (even if you’re just using their DNS servers, external domains sometimes require explicit association).
• Compare the DNS records (A, CNAME, MX, TTL values) side-by-side with your working domain. Even a tiny typo (like a missing dot in a CNAME) can cause DNS servers to refuse queries.
• Confirm that the GoDaddy nameservers listed in your OVH settings (nsxx.domaincontrol.com) exactly match the ones assigned to the domain in GoDaddy’s DNS Manager. It’s easy to mix up server numbers (e.g., ns12 vs ns21) by mistake.

2. Validate OVH’s DNS Change Propagation & Status #

Even 3 days post-change, some edge cases can delay propagation or block the update:

• Use the dig command (or nslookup on Windows) to check what nameservers global DNS sees for your domain. Run this in your terminal:

  dig your-domain.com NS @8.8.8.8
  

  If the output still shows OVH’s default nameservers, the change hasn’t propagated to root DNS servers. This could mean OVH didn’t process the change request—log into your OVH dashboard to check for pending verification steps (like email confirmations) or locked domain status (transfer locks can sometimes interfere with DNS changes).
• Check your domain’s WHOIS record to confirm the nameserver field reflects GoDaddy’s servers. If it still shows OVH’s, reach out to OVH support to ensure the change was submitted correctly.

3. Address the "REFUSED" RCODE from Zonemaster #

The REFUSED error means GoDaddy’s nameservers are rejecting queries for your domain, which points to a misconfiguration on their end:

• Test the query directly against GoDaddy’s nameservers from your local machine to rule out Zonemaster-specific blocks:

  dig your-domain.com NS @nsxx.domaincontrol.com
  

  If this also returns REFUSED, your domain isn’t properly registered in GoDaddy’s DNS infrastructure. GoDaddy’s support can check their backend to see why the server doesn’t recognize your domain.
• If your local query works but Zonemaster fails, it’s possible GoDaddy’s DNS has temporary IP-based restrictions. In this case, sharing the Zonemaster error with GoDaddy support will help them resolve the block.

4. Rule Out Domain-Specific Restrictions #

• Check if the problematic domain has any special status in OVH (e.g., pending verification, expired, or under dispute). Even a minor flag can prevent DNS changes from taking effect.
• Ensure the domain isn’t locked in GoDaddy’s system (if you’ve ever associated it with your account before) or in OVH’s transfer lock settings. Locks can block DNS server updates even if you’re not transferring the domain itself.

5. Reach Out to Official Support #

If all self-checks come up empty, escalate to both providers:

• Share the Zonemaster error screenshot and domain status with GoDaddy support—they can access internal logs to see why their nameservers are refusing queries.
• Confirm with OVH that the DNS change request was successfully processed and pushed to the root DNS registry.

内容的提问来源于stack exchange，提问作者user3210787