Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A foolish question, but did cloudflare shutdown it's dns services (free or otherwise) without telling anyone?
I have been using xfinity now wifi pass, with an acceptable level of service. And using cloudflare dns (1.1.1.1 and 1.0.0.1) - standard dns udp:53 with dnssec.
But as of yesterday morning, many dns requests were being delayed by sometimes over 1 minute, and many other dns requests were failing completely after being delayed. And some being redirected through proxies to obviously wrong websites.
As of this morning, cloudflare dns is completely non-responsive. Both standard udp:53 dns and DoH tcp:443 (as implemented by Mozilla) fail on every request.
I am only able to post this message because I switched to xfinity's own dns servers (75.75.75.75 and 75.75.76.76).
A foolish question, but did cloudflare shutdown it's dns services (free or otherwise) without telling anyone?
I have been using xfinity now wifi pass, with an acceptable level of service. And using cloudflare dns (1.1.1.1 and 1.0.0.1) - standard dns udp:53 with dnssec.
But as of yesterday morning, many dns requests were being delayed by sometimes over 1 minute, and many other dns requests were failing completely after being delayed. And some being redirected through proxies to obviously wrong websites.
As of this morning, cloudflare dns is completely non-responsive. Both standard udp:53 dns and DoH tcp:443 (as implemented by Mozilla) fail on every request.
I am only able to post this message because I switched to xfinity's own dns servers (75.75.75.75 and 75.75.76.76).
Thank you both for answering, knowing that it was not happening to anyone else pointed me to focus my troubleshooting efforts at my end.
After several hours of troubleshooting, I found that the raspberry pi I have been using as a local dns cache with bind 9 had become hacked and seriously compromised. Must be from some remote hacker, because no one else but me had physical access.
The bind was 9.2 , an out of date version, because that is what apt-get installed last summer.
The raspberry did not even have sshd enabled. I configured it's memory card directly. So the security weakness must have been in bind 9.2
I think I will move away from using bind. Maybe unbound would be safer?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.