.local + DNS = weirdness
.local + DNS = weirdness
- Subject: .local + DNS = weirdness
- From: Eric Dahlman <email@hidden>
- Date: Fri, 29 Oct 2004 09:49:51 -0500
Howdy,
I have a network problem that I to my Unix eyes is very bizarre and my
only idea is that there is some nuance in the way name lookup works on
the Mac that is causing me problems. So here is the situation...
Until recently we have used DNS with names like machine.example.com for
machines on our internal network. This was changed recently so that
now only machines with external IP addresses are in the .com domain
everything on the private network has been moved to
machine.example.local. I am using "example.com" instead of our real
name to protect the innocent ;-)
All of the Linux and Windows machines have been fine with this change,
however, my Mac is not taking it so well. Some things work in this
environment but others do not and I am at a loss for an explanation at
the moment as it looks like DNS is set up properly. Here are some
examples.
Things that work:
dig machine.example.local
dig -x 192.168.172.188
nslookup machine.example.local
nslookup 192.168.172.188
Things that don't work:
Safari.app cannot find http://machine.example.local but the raw IP
works
ssh email@hidden fails with
ssh: machine.example.local: No address associated with nodename
curl machine.example.local
curl: (6) Couldn't resolve host 'machine.example.local'
Lots of other things fail similarly. At first brush it looked like a
DNS problem but the fact the dig and nslookup work shows that DNS is
working just fine. My only other idea is that the .local domain is
being handled specially to support rendezvous, if so how?
If it is a rendezvous thing are there any RFCs covering this behavior.
In my google searching I turned up several drafts for using .local as
your private internal TLD but nothing that was formalized. (To be
honest it was hard to come up with a good set of keywords to cut
through all the irrelevant hits on this topic.)
I would appreciate any insight you could give me on this to fix things
or to push back against the internal naming change. If it is that
latter I need some sort of support like an RFC to show that somehow
.local should be handled specially because without it the systems guys
will just say that it is because my Mac is non-standard and therefore
broken.
Thanks a bunch,
-Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden