.INTERNAL is now reserved for private-use applications
1–10 of 290 posts
Re: .INTERNAL is now reserved for private-use applications
#2Re: .INTERNAL is now reserved for private-use applications
#3Re: .INTERNAL is now reserved for private-use applications
#4Re: .INTERNAL is now reserved for private-use applications
#5Re: .INTERNAL is now reserved for private-use applications
#6Can we get .local or .l added for private-use applications too?
Re: .INTERNAL is now reserved for private-use applications
#7Can we get .local or .l added for private-use applications too?
Re: .INTERNAL is now reserved for private-use applications
#82. Sell to scammers.
3. Profit.
(I want to appreciate how hard it probably is for ICANN to figure out proper TLDs.)
Re: .INTERNAL is now reserved for private-use applications
#9Can we get .local or .l added for private-use applications too?
Is it not already? https://en.wikipedia.org/wiki/.local
Re: .INTERNAL is now reserved for private-use applications
#10I need a dumbed down version of this.
There are certain circumstances where private network operators may wish to use their own domain naming scheme that is not intended to be used or accessible by the global domain name system (DNS), such as within closed corporate or home networks.
The "internal" top-level domain is reserved to provide this purpose in the DNS. Such domains will not resolve in the global DNS, but can be configured within closed networks as the network operator sees fit.
This reservation is intended for a similar purpose that private-use IP address ranges that are set aside (e.g. [RFC1918]).