Draft: RFC 6761 handling for invalid and *.localhost #120376
Draft
+13
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft PR for issue #118569.
Motivation
RFC 6761 defines special-use domain names:
invalid
and*.invalid
must always return NXDOMAINlocalhost
and*.localhost
must always resolve to the loopback addressCurrently, .NET relies fully on the OS resolver, which may allow
invalid
to resolve if defined in/etc/hosts
or DNS, and may not handle*.localhost
consistently across platforms.Proposed approach
invalid
and*.invalid
before OS resolution → throwSocketException
withHostNotFound
(simulate NXDOMAIN).localhost
and*.localhost
before OS resolution → returnIPAddress.Loopback
andIPAddress.IPv6Loopback
.Status