ukTroubleshoot DNS, hosting and HTTPS
Check one layer at a time: account status, DNS, network access, hosting configuration and finally HTTPS. Use your own registered name in place of the examples.
1. Check the name in your account
Open My names. A selected or unpaid name is not an active service. Check payment confirmation, expiry and any suspension notice before changing DNS.
2. Compare authoritative DNS with cached answers
On a computer with dig installed, inspect the public answer and each authoritative server:
dig yourname.uk.app A
dig yourname.uk.app AAAA
dig @ns1.uk.app yourname.uk.app A
dig @ns2.uk.app yourname.uk.app ACompare addresses with your hosting configuration. If both authoritative servers have the new value but your normal resolver has the old one, wait for the previous TTL to expire. If the authoritative servers disagree, contact support with the results and time. On Windows, use Resolve-DnsName yourname.uk.app in PowerShell.
3. Match the symptom
The old parking page still appears
Check the A and AAAA records, browser cache and hosting assignment. A stale AAAA record can send IPv6 users to a different server even when the A record is correct.
DNS resolves, but the connection times out
Check the server listener, firewall, router port forwarding and public address. Test from mobile data. DDNS updates DNS; it does not bypass carrier-grade NAT or open ports. See home-server setup.
The host returns 403 or 404
The server is responding. Check that the full hostname is attached to the correct project or virtual host, and inspect access rules and deployment status. A correct DNS answer alone does not configure the website.
The browser reports a certificate error
Check that the certificate covers the exact hostname and is valid. Complete the host's ownership verification and certificate process. Do not disable certificate validation. .app browsers require HTTPS; see ACME setup.
DDNS says badauth, nohost or abuse
Use the full registered name as the username and its DDNS token as the password, not your account password. Check that the target hostname belongs to this name and that the name is active. Stop repeated failed updates and inspect the protocol response.
4. Send a useful support request
Include the full hostname, intended host, exact error, time and timezone, DNS results and whether it fails on another network. Use support. Remove passwords, private keys, tokens and personal information from logs.