I'd like to have a very short internal TLD, go
, pointed at a webserver hosting a URL redirection app. For instance, a user could type go/chat
or go/news
without the need to remember what the exact URL is.
I've set up my internal DNS server with a zone file as follows:
$ttl 3600
go. IN SOA localhost. dns.company.corp. (
1597456469
3600
600
1209600
3600 )
go. IN NS localhost.
@ IN A 10.0.88.10
From a Windows host using nslookup
, this appears to work perfectly:
>nslookup go
Server: dns1
Address: 10.0.40.10
Non-authoritative answer:
Name: go
Address: 10.0.88.10
(with similar results on Linux)
However, no web browsers I've tried are able to resolve this name correctly. Chrome, Firefox, Edge, and IE all act as if this http://go
domain name doesn't exist, that is, unless I include an extra period on the address (http://go.
), upon which it resolves properly.
I've already tried the basics. Flushed DNS, rebooted, etc.
What's the right way to allow a "naked" TLD like this to be resolvable? Is this even possible?