3 ms·
He’s using it as a subdomain.
by icedchai 3mo ago
He’s using it as a subdomain.
- 0xbadcafebee 3mo agoWhich can still cause problems depending on your search domain setting and resolver client
- icedchai 3mo agoI do the same thing and have never had a problem. Maybe I’ve just been lucky for 25+ years. Some hosts have a search path of “int.example.com, example.com”. Others are just “example.com”
- _bernd 3mo agoCould you give an example? I'm curious, too.
- throw0101d 3mo agoIf you generally had "search example.com" in you resolv.conf, and were in the habit of having "web01.dev" in places, behaviour may have changed if you were happen to be on a machine that had the "search" line missing (or something else).
- throw0101d 3mo ago> He’s using it as a subdomain. Lots of folks were using "dev" as a sub-domain which was fine until ICANN decide to give Google a TLD: * https://en.wikipedia.org/wiki/.dev https://en.wikipedia.org/wiki/.dev So if you generally had "search example.com" in you resolv.conf, and were in the habit of having "web01.dev" in places, behaviour may have changed if you were suddenly on a machine that had the "search" line missing (or something else).
- icedchai 3mo agoWhat you describe is a user and resolver configuration problem. There are 100's of TLDs and there's always a chance they will conflict with subdomains, either now or in the future as new TLDs are created. I've been using both "int" and "dev" as subdomains since at least 2000 and never had an issue.
- throw0101d 3mo ago> What you describe is a user and resolver configuration problem. That won't prevent me from getting a ticket saying "the network is down".
- icedchai 3mo agoOkay, I guess the only solution is to always use FQDNs.