3 ms·
A similar thing happened where I work. Say our domain name was `example.com`, we had a fleet of hosts at `foo.build.example.com`, `bar.build.example.com`. The i
by bityard 7y ago
A similar thing happened where I work. Say our domain name was `example.com`, we had a fleet of hosts at `foo.build.example.com`, `bar.build.example.com`. The internal network handed out `example.com` as the DNS search string but web browsers always try the FQDN first. On the day the `.build` gTLD went live, people who use short names in their URLs (just about everyone) could no longer access these hosts and I was the one who got to figure out why.
- bluejekyll 7y agoWhen creating test domains these RFCs should be followed: https://tools.ietf.org/html/rfc6761 https://tools.ietf.org/html/rfc6761 Which updated: https://tools.ietf.org/html/rfc2606 https://tools.ietf.org/html/rfc2606 Basically, there are only a few reserved TLDs, .example.[com.|org.|net.], .test., .invalid., and .localhost. (rfc2606). RFC6761 clarifies how each should be used.
- Sylamore 7y agoHis issue wasn't the domain they used becoming a TLD, his issue was a subdomain they used became a TLD and the DNS resolvers of his clients were not configured to append the parent domain first, probably the search list wasn't populated.
- bluejekyll 7y agoOh. I misunderstood that. Thanks for clarifying.