You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC 6761 Defines several DNS names to be handled specially by DNS resolution APIs and libraries:
localhost, and *.localhost should always resolve to respective loopback address
invalid and *.invalid should always resolve to NXDOMAIN response
Unfortunately, current OS-level resolution APIs on both Windows and Linux (I did not check MacOS, but I assume the situation is going to be identical to Linux) do not recognize subdomains of localhost or invalid as special, and forward the queries to the respective DNS server (which is against the RFC spec).
This feature would play well with dotnet/aspnetcore#62593, which introduces support for localhost subdomains was for local development.
RFC 6761 Defines several DNS names to be handled specially by DNS resolution APIs and libraries:
localhost, and*.localhostshould always resolve to respective loopback addressinvalidand*.invalidshould always resolve to NXDOMAIN responseUnfortunately, current OS-level resolution APIs on both Windows and Linux (I did not check MacOS, but I assume the situation is going to be identical to Linux) do not recognize subdomains of
localhostorinvalidas special, and forward the queries to the respective DNS server (which is against the RFC spec).This feature would play well with dotnet/aspnetcore#62593, which introduces support for localhost subdomains was for local development.