35

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?

tig
  • 4,803

4 Answers4

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.

Sandeep Bansal
  • 6,452
8

Fortunately there is a fairly simple workaround that doesn't involve code.

  1. Go to Settings
  2. Manage search engines...
  3. Add a new search engine and use these as the 3 values:
    a. Default
    b. %s
    c. http://%s/
  4. Make default
Hello71
  • 8,673
  • 5
  • 42
  • 45
simmbot
  • 181
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)

Community
  • 1
jessepinho
  • 151
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?

LawrenceC
  • 75,182