DNS / Domain / Transfer07.06.2026

The DNS has been changed several times, and some users are still seeing the old website

Analysis of a DNS issue: The domain has already been transferred, but some users are still being redirected to the old server, forms are working inconsistently, and the owner sees different versions of the site.

Describe a similar problemAll analyses

Introduction

When migrating a website, people often change the DNS “quickly and on the fly”: one record at the registrar, a second in the hosting control panel, and a third in the CDN. Everything seems fine for a while, but then it turns out that some users are seeing the old version of the site, while others are seeing the new one. It’s especially problematic if the forms on the old site are still active.

Symptoms

A typical scenario: the owner opens the website and sees the new version, the manager sees the old one, and the ad system is testing a third version. Emails may come from the old form, new leads may be routed to the new CRM, and the analytics system interprets these events unpredictably.

What is being checked

  • Which NS records are actually specified for the domain?
  • Is there an old DNS zone on the hosting server or in the CDN?
  • What A/AAAA/CNAME records are returned by different resolvers?
  • What is the TTL set to, and how long does it take for the update to propagate?
  • Is DNSSEC enabled with outdated keys?
  • Are there any wildcard entries or old subdomains left?
  • Where do forms, sitemaps, robots.txt, and canonical URLs lead?

Correction Process

First, the single source of truth is determined: where the DNS zone should be managed. Then, the responses from several public resolvers and authoritative NS servers are checked. Old conflicting records are removed, the TTL is set to a normal value, and unnecessary AAAA or wildcard records are disabled if they point to the wrong location. After that, forms and technical URLs are checked separately, because they may refer to the old domain or server.

Normal result

A normal outcome is one active DNS zone, clear records, a predictable TTL, and an external check. The old server is either offline, returns a correct redirect, or is closed to incoming requests.

Conclusion

The danger of DNS issues is that a website can “work” and “not work” at the same time. Until authoritative responses and actual resolvers have been verified, the migration cannot be considered complete.

Comments on the analysis

Comments appear after moderation. Technical details without passwords, tokens, or private links.