iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If your domain still shows the old site after you add hosting, first check which DNS server is authoritative and what answer it returns. If the authoritative record points to the wrong place, fix the active DNS zone; waiting will not help. If it points to the new host but some DNS resolvers still return the old answer, caching may be responsible, and the old record’s TTL is the key timing clue.
First identify what changed
Adding a hosting account does not automatically point your domain to it. Your domain’s DNS settings must direct visitors to the host, and the settings that matter are those served by the domain’s authoritative nameservers.
| Change you made | What it affects | What to check |
|---|---|---|
| Nameserver change | Moves DNS authority to a different provider. | At the registrar, confirm the domain uses the exact nameservers assigned by the intended DNS provider. Then check records in the zone served by those nameservers. |
| Record-only change | Changes a DNS answer inside the existing authoritative zone. | Confirm the A, AAAA, or CNAME record was edited in the active zone and matches the destination supplied by your host. |
These changes have different failure points: a nameserver change can fail at registrar delegation, while a record change can be made in the wrong or inactive DNS zone. See AWS’s DNS troubleshooting guide and Cloudflare’s pending nameserver guidance.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Check the authoritative DNS configuration
Confirm the domain’s nameservers
Look up the nameservers currently published for the domain and compare the full set with the values assigned by your DNS provider. At the registrar, verify that the change was saved for the correct domain and account and that any confirmation step was completed. A nameserver value entered in a panel is not necessarily published delegation.
#1 Best Overall
- DUAL-BAND WIFI 6 ROUTER: Wi-Fi 6(802.11ax) technology achieves faster speeds, greater capacity and reduced network congestion compared to the previous gen. All WiFi routers require a separate modem. Dual-Band WiFi routers do not support the 6 GHz band.
- AX1800: Enjoy smoother and more stable streaming, gaming, downloading with 1.8 Gbps total bandwidth (up to 1200 Mbps on 5 GHz and up to 574 Mbps on 2.4 GHz). Performance varies by conditions, distance to devices, and obstacles such as walls.
- CONNECT MORE DEVICES: Wi-Fi 6 technology communicates more data to more devices simultaneously using revolutionary OFDMA technology
- EXTENSIVE COVERAGE: Achieve the strong, reliable WiFi coverage with Archer AX1800 as it focuses signal strength to your devices far away using Beamforming technology, 4 high-gain antennas and an advanced front-end module (FEM) chipset
- OUR CYBERSECURITY COMMITMENT: TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
dig +short your-domain.com NSThis command, documented by DigitalOcean, shows the nameservers returned for the domain. If they do not match the intended provider’s assigned set, resolve the delegation at the registrar before editing records elsewhere.
Edit the zone that is actually in use
Once you know which nameservers are authoritative, make changes in the DNS zone served by them. Some providers let an account contain more than one zone for the same domain. Editing an unattached or duplicate zone has no effect on public DNS. AWS discusses this failure mode in its DNS troubleshooting guidance.
Verify the host’s required records
Compare the domain’s current A or AAAA address, or CNAME target, with the value supplied in your hosting account. Do not guess the destination: use the host’s instructions for your specific service. Check the apex domain (such as example.com) and www separately; they may have different records and can resolve differently.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- 𝐅𝐮𝐭𝐮𝐫𝐞-𝐑𝐞𝐚𝐝𝐲 𝐖𝐢-𝐅𝐢 𝟕 - Designed with the latest Wi-Fi 7 technology, featuring Multi-Link Operation (MLO), Multi-RUs, and 4K-QAM. Achieve optimized performance on latest WiFi 7 laptops and devices, like the iPhone 16 Pro, and Samsung Galaxy S24 Ultra.
- 𝟔-𝐒𝐭𝐫𝐞𝐚𝐦, 𝐃𝐮𝐚𝐥-𝐁𝐚𝐧𝐝 𝐖𝐢-𝐅𝐢 𝐰𝐢𝐭𝐡 𝟔.𝟓 𝐆𝐛𝐩𝐬 𝐓𝐨𝐭𝐚𝐥 𝐁𝐚𝐧𝐝𝐰𝐢𝐝𝐭𝐡 - Achieve full speeds of up to 5764 Mbps on the 5GHz band and 688 Mbps on the 2.4 GHz band with 6 streams. Enjoy seamless 4K/8K streaming, AR/VR gaming, and incredibly fast downloads/uploads.
- 𝐖𝐢𝐝𝐞 𝐂𝐨𝐯𝐞𝐫𝐚𝐠𝐞 𝐰𝐢𝐭𝐡 𝐒𝐭𝐫𝐨𝐧𝐠 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧 - Get up to 2,400 sq. ft. max coverage for up to 90 devices at a time. 6x high performance antennas and Beamforming technology, ensures reliable connections for remote workers, gamers, students, and more.
- 𝐔𝐥𝐭𝐫𝐚-𝐅𝐚𝐬𝐭 𝟐.𝟓 𝐆𝐛𝐩𝐬 𝐖𝐢𝐫𝐞𝐝 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 - 1x 2.5 Gbps WAN/LAN port, 1x 2.5 Gbps LAN port and 3x 1 Gbps LAN ports offer high-speed data transmissions.³ Integrate with a multi-gig modem for gigplus internet.
- 𝐎𝐮𝐫 𝐂𝐲𝐛𝐞𝐫𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐂𝐨𝐦𝐦𝐢𝐭𝐦𝐞𝐧𝐭 - TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
Compare authoritative answers with public resolvers
This comparison separates a configuration problem from a cached answer. Query the authoritative nameserver for the domain, then compare the result with at least two public resolvers and your local machine. Google’s Public DNS troubleshooting guide recommends comparing resolver behavior; it also notes that if other public resolvers encounter similar difficulties, the problem is most likely with the domain’s authoritative servers.
dig example.test. @resolver1.opendns.com.
dig example.test. @dns.quad9.net.
dig example.test. @one.one.one.one.Replace example.test. with your domain. These example queries, documented by Google, check three public resolvers. To query a particular authoritative server, use its actual hostname as the resolver in a dig query. Compare the returned address or record with the target your host provided.
- Authoritative answer is wrong: Correct the record in the active zone or fix the registrar delegation. Waiting will not correct incorrect source data.
- Authoritative answer is right, but some public resolvers return the old value: A cached answer may still be in use. Check the TTL on the old answer and allow that cache to expire.
- Resolvers return different answers: Check whether you have unsynchronized zones or more than one active authoritative provider, as well as caches that have not expired.
Use the symptom to choose the next check
| What you see | Likely area to investigate | Next action |
|---|---|---|
| Old IP or old website | An outdated record, an old answer cached by a resolver, or competing DNS zones. | Compare authoritative and recursive answers. Correct the active record if it is wrong; if only cached answers are old, check the prior TTL. |
| NXDOMAIN | The queried name may be missing from the active zone, or delegation may point somewhere that does not serve it. | Check the domain’s nameservers and confirm the queried name exists in the zone they serve. |
| SERVFAIL | DNSSEC validation can fail when delegation data at the registrar does not match DNSSEC data published by the new DNS provider. | Inspect the DS record at the registrar and confirm it matches the DNSKEY data for the active provider. See Cloudflare’s nameserver guidance and Google’s troubleshooting guide. |
| Different visitors reach different sites | Resolvers may have cached different answers, or multiple active providers may serve unsynchronized zones. | Use the intended provider’s complete nameserver set, or deliberately keep every active zone synchronized. DigitalOcean explains the risk of conflicting providers in its domain resolution guide. |
Check DNSSEC after a nameserver move
DNSSEC adds validation data to DNS. If a DS record left at the registrar points to the old provider while the new provider publishes different or no matching DNSKEY data, validating resolvers can reject the domain’s answers and return SERVFAIL.
Rank #3
- Next-Gen Gigabit Wi-Fi 6 Speeds: 2402 Mbps on 5 GHz and 574 Mbps on 2.4 GHz bands ensure smoother streaming and faster downloads; support VPN server and VPN client¹
- A More Responsive Experience: Enjoy smooth gaming, video streaming, and live feeds simultaneously. OFDMA makes your Wi-Fi stronger by allowing multiple clients to share one band at the same time, cutting latency and jitter.²
- Expanded Wi-Fi Coverage: 4 high-gain external antennas and Beamforming technology combine to extend strong, reliable, Wi-Fi throughout your home.
- Improved Battery Life: Target Wake Time helps your devices to communicate efficiently while consuming less power.
- Improved Cooling Design: No heat ups, no throttles. A larger heat sink and redefined case design cools the WiFi 6 system and enables your network to stay at top speeds in more versatile environments.
- Check whether DNSSEC is enabled and inspect the DS record published at the registrar. Google documents
dig DS example.comas a way to inspect DS data. - Compare the registrar’s DS information with the DNSSEC keys published by the active DNS provider. Follow the migration instructions from both providers; do not leave stale delegation data in place.
- If the DS record is stale, follow the registrar and provider’s process to remove or update it. Wait for cached stale DS data to clear before enabling DNSSEC again with data that matches the active zone.
dig DS example.comCloudflare advises disabling DNSSEC before replacing nameservers in its full-setup nameserver instructions, then enabling it after the new setup is active. Its pending nameserver guidance says cached stale DS records may take up to 24 hours to clear after removal. That is Cloudflare’s operational estimate, not a universal deadline.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsKnow when to wait—and what the timing means
“Propagation” usually describes caches continuing to serve DNS data they received before a change. A resolver can keep an old answer until that answer’s TTL expires; after expiration, it can fetch current data. Different resolvers may therefore return old and new answers at the same time. cPanel explains this behavior in its guide to domains resolving to an old IP after a DNS update.
There is no guaranteed global wait time. In its Route 53 troubleshooting context, AWS says registrar nameserver TTLs are typically 24 to 48 hours and that a nameserver change can take up to two days. These are AWS operational estimates, not promises for every registrar or domain. Cloudflare’s separate estimate for clearing cached stale DS data is up to 24 hours after removal, as noted above.
Rank #4
- Dual band router upgrades to 1200 Mbps high speed internet (300mbps for 2.4GHz plus 900Mbps for 5GHz), reducing buffering and ideal for 4K stream
- Full Gigabit Ports - Gigabit Router with 4 Gigabit LAN ports, ideal for any internet plan and allow you to directly connect your wired devices
- Boosted Coverage - Four external antennas equipped with Beamforming technology extend and concentrate the Wi-Fi signals
- MU-MIMO technology - (5GHz band) allows high speeds for multiple devices simultaneously
- Access Point Mode - Supports AP Mode to transform your wired connection into wireless network, an ideal wireless router for home
The TTL that matters for a cached answer is the TTL on the answer when the resolver cached it. Lowering the TTL after the old answer has already been cached does not shorten that existing cache’s remaining lifetime; AWS makes this point in its DNS troubleshooting guide. If the authoritative answer is already correct and only some resolvers are stale, use the old TTL as a practical waiting clue rather than repeatedly changing records.
Clear local cache only after checking public DNS
If public resolvers return the correct answer but your computer or browser does not, a local resolver or browser cache may be involved. Clearing local DNS cache can help test that one device, but it cannot repair incorrect registrar delegation or clear caches maintained by remote resolvers. Namecheap covers local checks and cache tools in its DNS propagation guide. Check public results first so you do not mistake a local fix for a domain-wide one.
Recommended Free Tools
Prepare future hosting moves before changing DNS
For a planned migration, configure the destination zone first and keep the old service available while cached answers may still send visitors there. Namecheap recommends lowering an A-record TTL ahead of a planned move and allowing time before changing nameservers. That preparation can help future cache lifetimes; it cannot erase an answer that a resolver already cached under the previous TTL.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
