Although domain verification is generally straightforward, entering the DNS records incorrectly can prevent us from verifying your domain, which is needed to send requests from your own email address.
Here are other reasons why a domain is not able to verify:
1. DNS Propagation Delay
• Issue: DNS changes can take time to propagate across the internet. Depending on your DNS provider, it could take up to 24-48 hours for the new DNS records to be recognized.
• Solution: Wait for full DNS propagation, which typically takes a few minutes to several hours, but can be longer depending on the TTL (Time-to-Live) value set in your DNS settings.
2. Incorrect DNS Record
• Issue: The DNS record may be entered incorrectly. Even a small typo or missing detail can prevent successful verification.
• Solution: Double-check the exact format and values provided by your service, such as:
• Correct record type (e.g., TXT, CNAME).
• Correct Host/Name field (e.g., @, _dmarc, etc.).
• Correct Value/Target field (e.g., verification token or server address).
Your domain provider may have specific guidelines for adding the HOST information.
Providers like Namecheap and GoDaddy often append the domain name automatically to the HOST. When entering the CNAME Host details, be sure to remove “.example.com” from the end.
3. Incorrect Host/Name Field
• Issue: Some DNS providers automatically append your domain name to the Host/Name field, leading to a misconfiguration (e.g., _dmarc.example.com.example.com).
• Solution: Ensure that you only include the subdomain or prefix required in the Host/Name field (e.g., _dmarc, www, or @ for root domain). Avoid duplicating the domain name if the DNS provider appends it automatically.
4. Wrong Record Type
• Issue: The wrong type of DNS record is being used. For example, adding an A record instead of a TXT or CNAME record.
• Solution: Confirm that you’re using the correct record type (e.g., TXT, CNAME) as specified by the service you’re verifying with.
5. TTL Too High
• Issue: A high TTL (Time-to-Live) setting means DNS changes may take longer to update and propagate.
• Solution: Set the TTL to a low value, such as 300 seconds (5 minutes), to ensure faster updates.
6. Multiple DNS Providers
• Issue: If your domain’s DNS is managed across multiple services (e.g., through a third-party DNS manager or a CDN), DNS records may not be properly propagated.
• Solution: Ensure that the DNS records are added to the correct DNS provider managing the domain’s authoritative records.
7. Conflicting Records
• Issue: If you have existing DNS records of the same type (e.g., multiple CNAME or TXT records), there may be a conflict preventing successful verification.
• Solution: Remove or modify conflicting records, or ensure that multiple TXT records coexist without conflicts (which is allowed for TXT records but may not be for others like CNAME).
8. Propagation to Incorrect Nameservers
• Issue: Your domain might be pointing to the wrong nameservers, or the DNS records are not being updated on the correct nameservers.
• Solution: Check that your domain is pointing to the correct nameservers (usually provided by your DNS host or registrar), and that any changes are made on those nameservers.
9. Case Sensitivity or Special Characters
• Issue: Some DNS providers may handle case sensitivity or special characters in unexpected ways, causing issues with DNS records.
• Solution: Ensure that you’re following any specific guidelines for case sensitivity or character handling, as provided by your service.
10. Cached DNS Records
• Issue: You may be seeing outdated DNS information due to cached DNS records on your local device or browser.
• Solution: Clear your DNS cache or use a DNS lookup tool to check the updated DNS records.
11. Record Not Published
• Issue: Sometimes, DNS changes might not be correctly published by your DNS provider.
• Solution: Check with your DNS provider to ensure that the DNS record has been correctly published and is visible on the internet.
12. Subdomain Verification
• Issue: If you’re trying to verify a subdomain, ensure that you’re adding the DNS record under the correct zone for the subdomain.
• Solution: Ensure that you’re adding the DNS record specifically for the subdomain (e.g., subdomain.example.com) and not the root domain (example.com).