>> Can you explain how this is relevant to the .internal discussion >> which is specifically reserved to be used in DNS? > >Within the context of .internal, I would like to remark browsers' role in this > >for internal domain names (currently e.g. .lan in my networks). So the web >browser has an omnibar, right. And depending on what you put into it, the >browser needs to decide whether it should execute a DNS lookup and HTTP >request, or treat it as a search query. For domains on .lan, it always seems >to need a trailing /, most of the time not even . apex cuts it here. Which is >annoying.
This is getting off topic because how an 'omnibar' works is not part of this working group. But it does raise the question, do browsers react differently depending on whether a name is present in the root or not? If I type foo.internal in a web browser does it react differently from, say, foo.amsterdam. I tried for my browser (Firefox) and got the same result. But maybe other browsers different. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
