3 ms·
systemd's resolved commonly uses 127.0.0.53, Given the deployment of systemd I would not really call that a niche cases in terms of volume, but I do agree in ge
by benjojo12 2y ago
systemd's resolved commonly uses 127.0.0.53, Given the deployment of systemd I would not really call that a niche cases in terms of volume, but I do agree in general that 127.0.0.0/24 would in theory be enough. However the whole discussion on repurposing 127.0.0.0/8 is mostly academic as it will be basically impossible to use reliably
- greyface- 2y agoMy plot to pretend systemd doesn't exist has been foiled once again! Agreed that it would be impractical to actually use these. Maybe for linknets?
- itchyouch 2y agoGive it to someone like Google and I’m sure every corporate ceo will demand that Google.com loads from their infrastructure.
- tgsovlerkhgsel 2y agoExcept someone like Google would likely also want their site to work, and thus I expect them to be unwilling to use such a problematic IP. If any big site (or even better, many big sites together) were willing to go that far, a much better measure would be announcing that they'll go IPv6-only on the next IPv6 day. Just for that day. And then again the next year, but for a week. Then for a month the year after. Then permanently. That would give ISPs the kick in the butt to fix it, because nobody wants their hotline to field a day full of "my Internet doesn't work" calls, only to then have to fix it anyways because otherwise it'll be a week next time.