Score:-1

Wrong results after DNS Zone transfer with NS records being updated properly

dk flag

I migrated a DNS Zone example.org from one provider (foo.tld) to another one (bar.tld) one week ago.

To test the successful transition, I created a new TXT record test.example.org on bar's backend with a nonempty value.

The result is unexpected and strange, no matter what nameserver I am using (Google, Cloudflare, my ISP):

  • If I query dig example.org NS, I get the (updated) result of dns1.bar.tld, dns2.bar.tld
  • If I query dig example.org SOA, I get the old result from foo.tld, even though it only as a TTL of 21600, and a week has passed
  • If I query dig test.example.org TXT, no record is found

If I directly query bar.tld's NS servers (e.g. dig example.org SOA @dns1.bar.tld) everything works properly. How can it be, that the NS records are valid, but neither the SOA record, nor the newly created record are propery found / updated?

I tried to invalidate the Google DNS & Cloudflare caches, but it didn't help.

anx avatar
fr flag
anx
You might find [this tool](https://zonemaster.net/domain_check) useful. Please edit your question to include the actual name, so answers are not limited to speculation.
cn flag
Has the delegation been updated to refer to the new nameservers (through the registrar, as opposed to through the old dns service... potentially the same party but in that case different parts of the interface)?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.