5 ms·
pls excuse my aged brain, now with a new blood clot. IIRC adding 0.0.0.0 0.0.0.0 to your hosts file helps ??? On macOS; % ping 0.0.0.0 PING 0.0.0.0 (0.0.0.0)
by archo 2y ago
pls excuse my aged brain, now with a new blood clot.
IIRC adding 0.0.0.0 0.0.0.0 to your hosts file helps ???
On macOS;
% ping 0.0.0.0
PING 0.0.0.0 (0.0.0.0): 56 data bytes
ping: sendto: Socket is not connected
ping: sendto: Socket is not connected
Request timeout for icmp_seq 0
ping: sendto: Socket is not connected
Request timeout for icmp_seq 1
ping: sendto: Socket is not connected
Request timeout for icmp_seq 2
ping: sendto: Socket is not connected
Request timeout for icmp_seq 3
% ping 0
PING 0 (0.0.0.0): 56 data bytes
ping: sendto: Socket is not connected
ping: sendto: Socket is not connected
Request timeout for icmp_seq 0
ping: sendto: Socket is not connected
Request timeout for icmp_seq 1
ping: sendto: Socket is not connected
Request timeout for icmp_seq 2
ping: sendto: Socket is not connected
Request timeout for icmp_seq 3
ping: sendto: Socket is not connected
Is this correct ???
- TacticalCoder 2y ago> IIRC adding 0.0.0.0 0.0.0.0 to your hosts file helps ? Yup because typically you're not running a webserver on 0.0.0.0, especially not one that listen on ports 80/443 (say in dev you may be listening to 8080 or something). I mean: on Linux if you ping 0.0.0.0 (or the shortcut "ping 0"), you'll be getting answers from 127.0.0.1. But as I don't run a webserver on my machine (except a dev one at times, on a specific port which is not 80/443/8080 etc.), routing domains to 0.0.0.0 still works. I also used in the past dnsmasq to automatically reply NX_DOMAIN when the browser attempts to resolve 0.0.0.0 but atm I'm not even bothering (maybe I should do it again after reading TFA though). P.S: it's another aging brain answering, so take this with a grain of salt