Unified Root - Domain Configuration Issue

[Joe Baptista]

So a little more testing using firefox as an application gives us some
interesting results.  Using the .TM TLD I entered http://tm/ into my
browsers.  It did not work.  Firefox replaced http://tm/ with
http://www.tm.com/ - which is not the web site I wanted to reach.

However - if we qualify the TLD by adding a "." to the end, i.e.
http://tm./it does work under firefox and I get connected to the
correct site.

The same applies to ping.  If we just use TM we get this result:

baptista at baptista-laptop:/tmp/test.temp$ ping tm
ping: unknown host tm

however if we add the "." to the end of TM - it works, example:

baptista at baptista-laptop:/tmp/test.temp$ ping tm.
PING tm (193.223.78.213) 56(84) bytes of data.
64 bytes from serv213.icb.co.uk (193.223.78.213): icmp_seq=1 ttl=51
time=96.2 ms

Like I said - not recommended - but it does work - sort of.

regards
joe baptista

On Mon, Jan 19, 2009 at 11:02 AM, Joe Baptista <baptista at publicroot.org>wrote:

> Well - like I said below - it is not recommended to simply use http://tld/- however there are a few IANA TLDs that in fact are setup with A records
> associated with TLDs.  Just did a test out of curiosity and found the
> following ccTLDs with A records.
>
> AC.   86400 IN A 193.223.78.210
> AF.   86400 IN A 65.219.4.91
> AI.   14400 IN A 209.59.119.34
> BI.   38400 IN A 196.2.8.205
> CM.   3600 IN A 195.24.192.17
> DK.   86400 IN A 193.163.102.23
> HK.   604800 IN A 203.119.2.28
> IO.   604800 IN A 193.223.78.212
> PH.   86400 IN A 203.119.4.7
> PN.   43200 IN A 80.68.93.100
> PW.   600 IN A 203.199.114.33
> SH.   86400 IN A 64.251.31.234
> TM.   86400 IN A 193.223.78.213
> UZ.   14400 IN A 195.158.1.25
> WS.   21600 IN A 63.101.245.10
>
> Cheers
> Joe Baptista
>
>
> On Sun, Jan 18, 2009 at 9:49 PM, Joe Baptista <baptista at publicroot.org>wrote:
>
>>
>>
>> On Sun, Jan 18, 2009 at 9:39 PM, Mark Andrews <Mark_Andrews at isc.org>wrote:
>>
>>>
>>>
>>>         http://tld and user at tld can *never* work *reliably* as they
>>>        would cause namespace clashes.   Single label represent local
>>>        names not global names.
>>
>>
>> Thats incorrect.  It does work but is not recommended because it does not
>> always work depending on the application.  If the application relies solely
>> on gethostbyname then it will probably work - but some applications do a bit
>> more checking of the domain name and not all applications will allow it.
>>
>> cheers
>> 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 (360) 526-6077 (extension 052)
>>     Fax: +1 (509) 479-0084
>>
>>
>
>
> --
> 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 (360) 526-6077 (extension 052)
>     Fax: +1 (509) 479-0084
>
>


-- 
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 (360) 526-6077 (extension 052)
    Fax: +1 (509) 479-0084
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20090119/80f57d9b/attachment.html>