15

CDN

Last Update 2 months ago

I Don't Remember My Password What Can I Do If I Haven't Received my Verification Email How Can I Check if ClearFront is Optimizing & Delivering my Images in WebP Format? CDN Accelerated DNS Record SSL Issue Troubleshooting My Domain is Unavailable on the Internet

My Domain is Unavailable on the Internet

This article lists common reasons for issues with your domain not being reachable on the internet. An example of this would be the browser returning an ERR_NAME_NOT_RESOLVED error.


Your nameservers are not configured correctly at your registrar

One common reason for DNS issues is a misconfiguration of your nameservers at your domain registrar. To activate ClearFront DNS, your domain needs to be correctly configured with the nameservers provided in the DNS panel for your domain. Commonly, this would be kiki.cfplatform.xyz and coco.cfplatform.xyz. If your domain was not configured correctly with these nameservers, resolvers will not be able to route queries to ClearFront DNS.

Some registrars do not have an immediate nameserver switchover (in some cases up to 24hrs+), so you will need to monitor the state of the registrars nameserver records.


You are missing glue records for custom nameservers

If you have configured custom nameservers for a domain such as in the control panel that is pointing back to your own domain, such as https://mywebsite.com/ in the ClarForont control panel that is pointing back to your own domain, such as https://ns1.mywebsite.com/ , you will need to configure the correct glue records first. Glue records allow resolvers to find the DNS network responsible to resolve the domain by hinting the IP records with the domain itself.

Additionally, if the hostnames for the custom nameservers must contain the appropriate A records that point to the same IP addresses as the glue records.

If these glue records have not been correctly configured with your domain registrar, resolvers will not be able to find your domain name.


You transferred the domain from another DNS service without disabling DNSSEC

If you recently migrated from a different DNS service that had DNSSEC enabled and did not disable the DNSSEC prior to the migration, this will break the chain of trust and force resolvers to reject queries responded by ClearFront DNS. To resolve this, make sure your previous DNS service has DNSSEC disabled. Ensure to re-enable DNSSEC on ClearFront DNS and add those records to your registrar afterwards if required.


An exception happened in your DNS script

If you are using the scriptable ClearFront DNS records, it's possible that the script is throwing an exception. This would make ClearFront DNS unable to return records to the user.


You are missing A, CNAME, or AAAA records

In order for a domain name to be reachable by a web browser or other applications, the appropriate DNS records need to be set up for that domain. If you are trying to reach a domain https://mywebsite.com/ , you would need to create an A record to point to an IP address such as 185.188.10.122.


You have a typo in your domain name

One reason that a domain might be unreachable would be a type in the created DNS zone or record. When troubleshooting connectivity, please make sure the requested domain matches the requested query exactly.


Debugging Tools

ClearFront has a suite of tools to help aid you in the transition, including DNS tools found here: https://mxtoolbox.com/DNSLookup.aspx . You can perform a global NS lookup on your domain to check propagation status for example, or verify other records are working as expected in certain regions.

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us