Teach Google Chrome to understand custom TLD
Hire the world's top talent on demand or became one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Future Grid Looping
--
Chapters
00:00 Teach Google Chrome To Understand Custom Tld
00:45 Accepted Answer Score 15
01:03 Answer 2 Score 0
01:22 Answer 3 Score 8
01:50 Answer 4 Score 5
02:16 Thank you
--
Full question
https://superuser.com/questions/274562/t...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#googlechrome #tld
#avk47
ACCEPTED ANSWER
Score 15
According to this bug posted: http://code.google.com/p/chromium/issues/detail?id=30636
Google will not be fixing the issue you have. The only method should be to use http://example.nt I don't see why that won't work.
ANSWER 2
Score 8
Fortunately there is a fairly simple workaround that doesn't involve code.
- Go to Settings
- Manage search engines...
- Add a new search engine and use these as the 3 values:
a. Default
b. %s
c.http://%s/ - Make default
ANSWER 3
Score 5
Similarly to simmbot, I've created a search engine with a keyword of 'l' (my local TLD is .l). The URL is http://%s.l. Then, I simply type "l mysite" in the address bar and it takes me to mysite.l.
Alternatively, you can simply add a slash at the end, and Chrome won't consider it a search. (See https://stackoverflow.com/a/7877750/974981)
ANSWER 4
Score 0
I run my own local DNS server (BIND on Linux) which resolves LAN domains using a custom TLD and then recurses non-LAN to OpenDNS. I've never experienced any issues like this. Are you sure your local DNS is correctly resolving .nt domains?