up vote 6 down vote favorite
1
share [g+] share [fb]

For development on local machine I've set domains with custom top level domain .nt. But Google Chrome doesn't know about this top level domain, so, if I enter example.nt in location bar, then google doesn't open that location, but opens search with that string (though it shows a bar proposing that I wanted to open location instead of searching if DNS request for that location satisfies). So I can either type http://example.nt, type example.nt/ or open that location to teach Google Chrome, but in any case there will be slash at the end of location. All this is not very convenient, also I don't like this slash, is it possible to tell Google Chrome, that .nt is a normal TLD, so just open locations in with it?

link|improve this question
62% accept rate
feedback

2 Answers

up vote 4 down vote accepted

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.

link|improve this answer
That will work, but people aren't in the habit if typing "http://" in front of everything. When was the last time you wanted to go to a site and started typing "http://"? – Asa Ayers Oct 10 '11 at 16:56
feedback
up vote 0 down vote

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?

link|improve this answer
I use /etc/hosts with script generated entries and all domains are resolved correctly. – tig Apr 25 '11 at 13:23
The thing is with /etc/hosts is that a program can't resolve things in it and get the nameserver of a specific domain, I believe. e.g., if you have "example.nt" in your hosts file, it can't ask which nameserver is responsible for the ".nt" domain, because there is none. Chrome does some DNS checks to work around DNS providers that redirect bad DNS resolutions to ad pages and I'll bet this has something to do with it. You might try running a local DNS server. – ultrasawblade Apr 25 '11 at 14:33
But Chrome proposes me to go to location if domain is present in /etc/hosts. Also the question was more on possibility to add .nt to list of "normal top level domains", if I try to go to location aristnraisetnrast.com, which dose not exist, Chrome doesn't search for it, I just get "This webpage is not available", but if I try domain.nt which does exist, than I get a search page. – tig Apr 25 '11 at 15:56
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.