DNS Resolution Error
Good morning lovely people. To preface, my knowledge and usage of Cloudflare is strictly related to domains and DNS.
When I woke up this morning, for Reasons Unknown, one of my subdomains is mysteriously resolving to the wrong IP address(es)
* Cloudflare itself is controlling DNS for my domains. Everything online looks correct. As it should, because nothing has been changed recently.
* The subdomain resolves incorrectly for both myself, and my coworkers 3000 miles away, all on different devices, time zones, and networks.
* It resolves incorrectly when I lookup via 1.1.1.1, 1.0.0.1, and even a non-Cloudflare DNS provider like DNSWatch 84.200.69.80.
* I do not recognize the incorrect IP addresses being returned by DNS lookup.
* I do not have support with Cloudflare, so I'm unable to report this to them directly, or make official inquiries.
I have not seen a DNS resolution error like this in a very, very long time.
The only course of action I can think of is to alter my A records in Cloudflare to another IP, then back again to the real IP, and just hope the changes "stick" and fix the issue.
But before I did that (potentially destroying evidence of the bug), I thought I'd ask you all "Hey, what's up with this?"
Thanks in advance.
When I woke up this morning, for Reasons Unknown, one of my subdomains is mysteriously resolving to the wrong IP address(es)
* Cloudflare itself is controlling DNS for my domains. Everything online looks correct. As it should, because nothing has been changed recently.
* The subdomain resolves incorrectly for both myself, and my coworkers 3000 miles away, all on different devices, time zones, and networks.
* It resolves incorrectly when I lookup via 1.1.1.1, 1.0.0.1, and even a non-Cloudflare DNS provider like DNSWatch 84.200.69.80.
* I do not recognize the incorrect IP addresses being returned by DNS lookup.
* I do not have support with Cloudflare, so I'm unable to report this to them directly, or make official inquiries.
I have not seen a DNS resolution error like this in a very, very long time.
The only course of action I can think of is to alter my A records in Cloudflare to another IP, then back again to the real IP, and just hope the changes "stick" and fix the issue.
But before I did that (potentially destroying evidence of the bug), I thought I'd ask you all "Hey, what's up with this?"
Thanks in advance.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
