If a new site is not loading, the first question is simple: does the domain actually point to the TekLan hosting server? DNS, browser cache, old IPv6 records, and www differences can all make this less obvious than it should be.
Check the Active Nameservers
Nameservers decide where DNS is managed. Check them first:
dig example.co.uk NS
If the nameservers are TekLan nameservers, manage DNS through the TekLan/Enhance setup. If they belong to another provider, update records at that provider instead.
Check the Root Domain A Record
The root domain is the version without www.
dig example.co.uk A
The returned IP address should match the IP address assigned to your TekLan hosting website. You can find the expected IP in Enhance by opening the website and checking its domain or DNS details.
Check the www Record
The www hostname is separate. It may be an A record or a CNAME.
dig www.example.co.uk A
dig www.example.co.uk CNAME
If the root works but www does not, check the www record and make sure the hostname is added to the website inside Enhance where required.
Check IPv6 Records
A stale AAAA record can send some visitors to an old server even when the A record is correct.
dig example.co.uk AAAA
dig www.example.co.uk AAAA
If you are not intentionally using IPv6 for the site, remove old AAAA records or update them to the correct destination.
Check Authoritative DNS
If public resolvers disagree, query the authoritative nameserver directly. First find it:
dig example.co.uk NS
Then query one nameserver from that result:
dig @ns1.example-dns-provider.co.uk example.co.uk A
If the authoritative answer is correct but public resolvers still show the old value, wait for the old TTL to expire.
Check the Website Response
Once DNS points at the right IP, check the web server response:
curl -I https://example.co.uk
A DNS record can be correct while the website still shows a holding page, SSL error, redirect loop, or old cached content. If DNS is right but the page is wrong, check the website inside Enhance, SSL status, redirects, and cache.
Common Mistakes
- Changing DNS at a provider that is not the active nameserver provider.
- Updating the root domain but forgetting
www. - Leaving an old
AAAArecord in place. - Expecting DNS to update before the old TTL expires.
- Testing in a browser that still has cached redirects.
Related TekLan Guides
Use Pointing Your Domain to Your Hosting for the setup steps and How to Check DNS Propagation Properly for a deeper DNS check process.