Thank you for flushing it, I can see that the nodes which were
previously failing are now working.
I also appreciate the logs, which confirms my fear that the old NS set
was stuck in the cache with what's left of the parent's TTL. That's sort
of good news in the short term since at least we know now that the
problem will go away in time. It's better news longer term since it
tells me that my ultra-paranoid step of adding both sets to the parent
isn't so paranoid after all, and will work to smooth the transitions for
the other sites.
Wasn't there a move away from parent-centric in the past? Did I miss a
memo?
Thanks again,
Doug
On 2020-04-02 13:49, Brian Somers wrote:
I’ve flushed shopdisney.co.uk/NS globally. Should work now for
Umbrella/OpenDNS/Cisco
On Apr 2, 2020, at 1:36 PM, Brian Somers <[email protected]> wrote:
This is what I see with diagnostics turned up:
shopdisney.co.uk. 0 IN TXT "RESOLVER:
shopdisney.co.uk IN NS ns1.disneyinternational.net"
shopdisney.co.uk. 0 IN TXT "RESOLVER:
shopdisney.co.uk IN NS ns2.disneyinternational.net"
shopdisney.co.uk. 0 IN TXT "RESOLVER:
shopdisney.co.uk IN NS ns3.disneyinternational.net"
shopdisney.co.uk. 0 IN TXT "RESOLVER:
shopdisney.co.uk IN NS ns4.disneyinternational.net"
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
