LOCALHOST and LOCAL TLDs added to FCFS PublicRoot
Joe Baptista
Today the FCFS PublicRoot has added support for the .LOCALHOST and
.LOCAL TLDs. .LOCALHOST defines the local loop on all computers and
.LOCAL is an internal MicroSoft TLD. We are also considering adding
support for the MicroSoft internal TLD .GBL once the .LOCAL tests
conclude successfully.
regards
joe baptista
--
Joe Baptista www.publicroot.org
PublicRoot Consortium
----------------------------------------------------------------
The future of the Internet is Open, Transparent, Inclusive,
Representative & Accountable to the Internet community @large.
----------------------------------------------------------------
Office: +1 (202) 517-1593
Fax: +1 (509) 479-0084
Joe Baptista
had a look at your hosts file but the only label in there is
.LOCALHOST. Are you sure you don't mean LOCALHOST as opposed to LOCAL.
The reason why LOCALHOST is carried in the zone file is that CAIDA shows
a large number of queries to root servers are received for the LOCALHOST
TLD/host. So it is good for root servers to know the answer to the
LOCALHOST question since it's always 127.0.0.1.
So thats a necessary housekeeping function. The RFC state that
localhost should never be seen on the net. Thats the rational for not
including it anywhere but on the local host or local network. However
the evidence shows that LOCALHOST is misconfigured on many hundreds of
thousands of computers that it is best that a root known the answer so
as to decrease and eliminate lookup errors.
Now LOCAL is a different kettle of fish. That TLD has some special use
in some microsoft applications. The applications expect an NXDOMAIN
response to queries - or no response - I'm not to sure on that. So if
you have more details on .LOCAL please share.
regards
joe baptista
p.s. Roeland and all who are participating here. If you want to join
the Inclusive Name Space WorkGroup your welcomed to do so. This is the
place were we only discuss the technical end of the INS.
Roeland Meyer wrote:
>No it isn't. I'll send you my file but my servers are so heavily
>modified that it may not be valid for use as standard practice. I
>don't have a clean installed system at the moment. They are all
>corrupted, by me ;)
>
>
>
>
>--
>R O E L A N D M J M E Y E R
>Avenue Viollier 24
>1260 Nyon, Switzerland
>Mob: +41(0)79295 14 68
>Web: http://www.roelandmeyer.org
>Mail: mailto:roel...@roelandmeyer.org
>
>
>
>
>
>>-----Original Message-----
>>From: tlda-m...@googlegroups.com
>>[mailto:tlda-m...@googlegroups.com]On Behalf Of Joe Baptista
>>Sent: Friday, October 26, 2007 8:14 AM
>>To: tlda-m...@googlegroups.com
>>Cc: ins...@googlegroups.com
>>Subject: Re: LOCALHOST and LOCAL TLDs added to FCFS PublicRoot
>>
>>
>>Roeland - could you please send me a copy of one of
>>these hosts.txt
>>files that contain the .LOCAL reference. At this time
>>the .LOCAL is
>>resolved off of the microsoft servers.
>>
>>Thanks
>>joe
>>
>>Roeland Meyer wrote:
>>
>>
>>
>>>.LOCAL is already a hosts.txt file on many Windows and Linux
>>>boxen. There're reasons why it isn't in the standard root. You
>>>might want to seriously re-consider this.
>>>
>>>--
>>>R O E L A N D M J M E Y E R
>>>Avenue Viollier 24
>>>1260 Nyon, Switzerland
>>>Mob: +41(0)79295 14 68
>>>Web: http://www.roelandmeyer.org
>>>Mail: mailto:roel...@roelandmeyer.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: tlda-m...@googlegroups.com
>>>>[mailto:tlda-m...@googlegroups.com]On Behalf Of
>>>>
>>>>
>>Joe Baptista
>>
>>
>>>>Sent: Friday, October 26, 2007 6:04 AM
>>>>To: ins...@googlegroups.com
>>>>Cc: tlda-m...@googlegroups.com; uca...@googlegroups.com
>>>>Subject: LOCALHOST and LOCAL TLDs added to FCFS PublicRoot
>>>--
>>>http://home.caselle-vpn.net
>>>Complaints mailto:ab...@caselle-vpn.net
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>--
>>Joe Baptista www.publicroot.org
>>PublicRoot Consortium
>>----------------------------------------------------------------
>>The future of the Internet is Open, Transparent, Inclusive,
>>Representative & Accountable to the Internet community @large.
>>----------------------------------------------------------------
>> Office: +1 (202) 517-1593
>> Fax: +1 (509) 479-0084
>>
>>
>>
>>
>
>
>
>
>--
>http://home.caselle-vpn.net
>Complaints mailto:ab...@caselle-vpn.net