61–70 of 87 posts
I switched to 1.1.1.1 when it was released and since I’ve had multiple issues with free wifis where they would fail to hijack my dns requests to allow me to login to their portal. I Assume this is a good thing but can someone explain to me why this is happening and what’s the state on improving these wifi portals? PS: sorry for hijacking the thread.
I switched to 1.1.1.1 when it was released and since I’ve had multiple issues with free wifis where they would fail to hijack my dns requests to allow me to login to their portal. I Assume this is a good thing but can someone explain to me why this is happening and what’s the state on improving these wifi portals? PS: sorry for hijacking the thread.
Earlier quoted context omitted.
In 2000 the answer would be no. In 2018 I think it is. Things change in a time when you would freak getting up in the morning and say google.com did not work.
Humans react, analyze, and communicate at the same speed we did in 2000. Our tools may have gotten better, but that only cuts down on part of the process. Automated processes can only mitigate so many edge cases. Even then, humans need to be involved, and that slows things down.
Another example - I can record a video and broadcast internationally, translated on the fly into dozens of languages, effectively communicating with significantly more people than if I could not harness that technical capability. In 2000 that communication process would have been orders of magnitude longer. (Did they have on-the-wire translation then? Idk, just making an assumption to illustrate my point.)
What's interesting here is that the automatic cure (DDoS protection) was worse than the disease (even if there was an attack, blocking all access to the DNS servers is potentially worse than letting them get overloaded). I wonder if it would be possible to express the idea that if a block being applied drops traffic well below expected levels, it must be a mistake?
Doesn't seem fixed, still can't resolve archive.is cloudflare is giving off cloudflare DNS web errors. https://i.imgur.com/APpQPTJ.png
Doesn't seem fixed, still can't resolve archive.is cloudflare is giving off cloudflare DNS web errors. https://i.imgur.com/APpQPTJ.png
https://community.cloudflare.com/t/archive-is-error-1001/182...
I switched to 1.1.1.1 when it was released and since I’ve had multiple issues with free wifis where they would fail to hijack my dns requests to allow me to login to their portal. I Assume this is a good thing but can someone explain to me why this is happening and what’s the state on improving these wifi portals? PS: sorry for hijacking the thread.
In the meantime, have you tried adding other addresses such as 1.0.0.1, 8.8.8.8, or 9.9.9.9 to see whether the fallback works?
Earlier quoted context omitted.
I read on the Pi-Hole forums that 'fallback' is a misleading term because clients don't work that way - they will happily spread requests between two functioning DNS servers. Can anyone confirm this or provide further insight?
Different OSes handle it differently. Windows tries the primary, waits 1 second and then starts trying secondaries.
This is a great write up. It's also why the DNS root servers have a policy of surviving DDoS through massively over-provisioned, multi-org, anycasted redundancy rather this sort of smart DDoS mitigation that drops traffic: DNS is so critical that any risk of dropping real traffic is unacceptable. (obviously, such a scale is impractical for 99% of services) A good takeaway from this outage for the average user would b…
Or 9.9.9.9 if you're not as comfortable with Google services.
