It probably depends on how your O/S handles the resolution - typically
Windows systems will try and resolve a dot-less name using a local LAN
broadcast looking typically for a PC on the same LAN segment by that
name - but it will depend on your config (e.g. domain controller or not,
LAN Manager settings etc.etc YMMV etc)
IMHO, if they work or not, BRAND holders should simply be aware they
probably won't, but they can try if they like, its within RFC.
I guess the other issue is do you allow a GLUE record for it in the ROOT
zone and if so, how often will you allow those to be updated.
On Chrome+Win7 I get different responses for http://dk/ , http://dk./
and https://dk./ .... but none work :)
On 21/09/2012 10:07, Bart Smit wrote:
Phil Regnauld wrote:
Surprised no one's brought up http://dk/ as an already existing scenario
that doesn't work (try it in various browsers).
Bad example. The first *four* browsers I tried (firefox, chrome, safari,
and opera on osx) handle this perfectly.
B
_______________________________________________
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
_______________________________________________
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
