Troubleshoot websites and DNS

Most checks here use dig. Add @ns1.coritan.com to ask Coritan's nameserver directly, which skips the answers that resolvers keep in their cache.

Check which nameservers answer for the domain:

dig example.com NS +short

If the answer does not list Coritan's nameservers, ns1.coritan.com to ns8.coritan.com, resolvers never ask Coritan. Set the nameservers at the domain's registrar (Add a domain you already own), or on the Settings tab for a domain registered with Coritan (Change a domain's nameservers).

If Coritan's nameservers are listed, ask one for the name:

dig @ns1.coritan.com www.example.com A

An NXDOMAIN status means the zone has no record at that name. Add one on the DNS tab (Add, edit and delete DNS records).

Coritan's nameservers refuse queries for a domain that has no active zone here. The zone was never added, was deleted, or is suspended with its service. The DNS zone card on the domain's Settings tab shows a suspended zone's status. Failed payments and suspended services explains how to get a service running again.

A resolver that checks DNSSEC answers SERVFAIL when the DS record at the registrar does not match the zone's key. To confirm, ask with checking turned off:

dig example.com A +cd +short

If this gives an address while a plain query gives SERVFAIL, DNSSEC is the cause. Replace the DS records at the registrar with the ones on the DS records for the registrar card, and delete any DS record left by a previous DNS provider (Set up DNSSEC). A zone you delete and add again gets new keys, so it needs new DS records too.

Coritan's nameservers answer with a change as soon as you save it. Resolvers that cached the old answer keep it until its TTL runs out. Compare the answer from ns1.coritan.com with your resolver's, and lower the TTL before your next planned change (TTL).

The error names the rule the record breaks, such as a CNAME at @ or a name that a load balancer owns. Add, edit and delete DNS records lists each error with its fix, and DNS record types gives the format for each type.

The import skips lines it cannot read and adds every record beside the ones the zone already has. Import and export a zone file explains what it reads and how to fix a file.

Open the load balancer's preview on the Load balancing tab to see which pool answers and why. Create a load balancer and the preview results explain each outcome.

The SSL tab shows the reason under The last request failed. The usual causes are a CAA record that does not allow Coritan's certificate authorities, a name that does not point at Coritan's edge for HTTP validation, and a TXT record that is missing or has the wrong value. Issue a certificate lists each error with its fix.

A certificate validated with a manual TXT record cannot renew on its own, and any renewal fails when validation no longer works. Renew or revoke a certificate explains what to do before the Expires date.

The edge has no valid certificate for the exact name the visitor opened. A certificate for example.com does not cover www.example.com, so each name needs its own. Check the name's certificate on the SSL tab, and issue one if it has none.

The name resolves to Coritan's edge, but no web proxy serves it. This happens after you delete a web proxy while the name's record stays proxied. Create a web proxy for the name, or turn Proxied off for its record on the DNS tab so the name resolves to your own address.

The WAF refused the request, or asked the visitor to prove they are human. Protect a website with the WAF explains both pages and what you can change.

Coritan does not move a transfer out of pending_transfer by itself. When your old registrar confirms that the domain has left, contact support so the registration can be made active (Transfer a domain to Coritan).

Renewing, the switches, the nameservers and the EPP code need the registration to be active. While it is expiring_soon, expired or pending_transfer, the dashboard cannot change them. Contact support if you need to (Statuses).