Noticed some very strange behaviour when looking at webpages within a new domain set up internally for a company project.
At first, it looked like the DNS was failing,
ping came back with :
dig web.internal.local returned the correct result. Very strange.
More strange was that the “Fedora Server” also on the same network
was returning the correct results for both, and both had the
same (NetworkManager generated) entries in
Have a look in the
/etc/nsswitch.conf file, in order to
see what the DNS resolution order is.
Failing desktop machine :
Working server machine :
Leads to the solution (helped by this helpful post) :
The base issue being that
.local domains are a special case for
If the company had chosen
.internal (or even
they would have been in the clear. Bad luck to have made such a reasonable choice,
which turned out to have been someone else’s special case…
blog comments powered by Disqus