nanog mailing list archives
Re: DoD IP Space
From: "Valdis Klētnieks" <valdis.kletnieks () vt edu>
Date: Mon, 15 Feb 2021 10:49:50 -0500
On Sun, 14 Feb 2021 22:25:56 -0800, William Herrin said:
This particular problem could be quickly resolved if the OSes still getting updates were updated to default name resolution to prioritize the IPv4 addresses instead. That would allow broken IPv6 configurations to exist without breaking the user's entire Internet experience. Which would allow them to leave it turned on so that it resumes working when the error is eventually found and fixed.
Oh, come on Bill. This ain't your first rodeo. You know damned well that if we do that, the errors are in fact *not* eventually found and fixed. In addition, if you do that, even once the error is fixed, the box will not know about that and will continue to use the IPv4 addresses.
Current thread:
- Re: DoD IP Space, (continued)
- Re: DoD IP Space Mark Tinka (Feb 14)
- Re: DoD IP Space Sabri Berisha (Feb 14)
- Re: DoD IP Space Mark Tinka (Feb 14)
- Re: DoD IP Space William Herrin (Feb 14)
- Re: DoD IP Space Mark Tinka (Feb 14)
- Re: DoD IP Space Mark Andrews (Feb 14)
- Re: DoD IP Space William Herrin (Feb 15)
- Re: DoD IP Space John Curran (Feb 15)
- Re: DoD IP Space Geoff Mulligan (Feb 15)
- Re: DoD IP Space Randy Bush (Feb 15)
- Re: DoD IP Space Valdis Klētnieks (Feb 15)
- Re: DoD IP Space William Herrin (Feb 15)
- Re: DoD IP Space nanog (Feb 15)
- Re: DoD IP Space Mark Tinka (Feb 15)
- Re: DoD IP Space Jay Hennigan (Feb 26)
- Re: DoD IP Space Mel Beckman (Feb 26)
- Re: DoD IP Space Daniel Seagraves (Feb 27)
- Re: DoD IP Space Mark Tinka (Feb 14)