On Fri, Apr 04, 2025 at 05:17:24AM -0400, gene heskett wrote: > On 4/3/25 09:29, Greg wrote: > > On 2025-04-03, Dan Purgert <d...@djph.net> wrote: > > > > > > That's what you want: as the address is in the 127.0.0.0 network, > > > > pinging it will ping itself, and it gets a reply. It doesn't > > > > require your LAN to be set up, and AIUI it's like localhost > > > > (127.0.0.1) in that it doesn't touch the network hardware. > > > Indeed, the entirety of 127.0.0.0/8 is the virtual loopback adapter > > > (i.e. "localhost"). > > Doubtless yet another fallacious notion, but I thought IPV6 opened up > > the flood gates of assigning "real" ip addresses to whatever the heck > > Gene's talking about. > > > > I guess it isn't happening any time soon. > The more rural WV areas are an ipv6 desert, and given Debian's penchant for > ipv6, its disabled here. I've no clue, but it seems to me that if it gets > no replies trying ipv6, it should fall back to ipv4.
The problem is what is "it". Currently it's each application (using some underlying library). The normal path is: - resolve the name (there you can get both A and AAAA records, if the programmers know what they are doing) - try one of them: which one first? Wait for some timeout (how long?) try next. - ideally, try all of them in parallel (suddenly you end up with an application written in non-blocking style or -GAH!- even some multi-threaded monster. The solution is underway, is called "happy eyeballs" [1] and will be here some day. At the DNS resolution level you can prioritise whatever suits you by editing /etc/gai.conf, which comes with a man page. Cheers [1] https://en.wikipedia.org/wiki/Happy_Eyeballs -- t
signature.asc
Description: PGP signature
