On Sun, Jan 24, 2021, at 3:21 AM, Tim via users wrote:
> On Sun, 2021-01-24 at 00:07 -0700, Joe Zeff wrote:
> > Or, you do the sensible thing and point said domain to 127.0.0.1, so
> > that it times out almost instantly.
>
> It doesn't. The web browser waits for something to answer it. Go on,
> try to get your web browser to connect to a non-existent server, it
> doesn't immediately stop looking.
My hosts file setup is working very quickly.
I can't remember why I stopped pointing to 127.* but something had me change to:
>route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.100.254 0.0.0.0 UG 600 0 0
wlp0s26f7u3
111.72.252.91 - 255.255.255.255 !H 0 - 0 -
[snip]
So you see that "111.72.252.91" is null routed.
In my hosts file I point to that IP:
>grep "^111.72.252.91" /etc/hosts | wc -l
11811
Using a sample name from that list I get a very quick fail with firefox:
Unable to connect
Firefox can’t establish a connection to the server at xads.zedo.com.
The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer’s network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.
--
Doug Herr
[email protected]
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
