← Back to context

Comment by 0xbadcafebee

2 days ago

Which can still cause problems depending on your search domain setting and resolver client

I 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”

Could you give an example? I'm curious, too.

  • 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 happen to be on a machine that had the "search" line missing (or something else).