Re: .local dns
Re: .local dns
- Subject: Re: .local dns
- From: Peter John Hill <email@hidden>
- Date: Mon, 9 Jun 2003 19:28:04 -0400
On Monday, June 9, 2003, at 04:44 PM, Joshua Graessley wrote:
Please don't cross post.
The question is relevant to both groups, IMHO, so I will cross post to
find the answer.
Use IP addresses or pick a different top level domain to usurp.
I disagree, so do:
Microsoft encourages the use of .local for private IP space,
http://support.microsoft.com/default.aspx?scid=kb;en-us;296250
DJ Bernstein also talks about using .local for a local tld (creator of
djbdns server)
http://cr.yp.to/djbdns/dot-local.html
and, the comp.protocols.tcp-ip.domains FAQ also recommends using .local
http://www.intac.com/~cdp/cptd-faq/section5.html#split_DNS
So, I think the Mac OS implementation is broken if it will not properly
resolve .local when I telnet
Putting mdns in the "order" creates a lot of problems. Instead of
opening that can of worms, mDNS uses the "local." top level domain to
indicate that the name has only local meaning and should be resolved
using mDNS.
I think that is a bad solution. local. can have meaning beyond the
subnet. In any AS, it is perfectly fine to route 1918 address space, as
long as it is blocked beyond the border. Of course a good dns server
admin will also block queries for PTR lookups to those addresses at
their border.
http://www.caida.org/outreach/presentations/ietf0112/dns.damage.html
I was not able to find any RFC or current internet draft that is
claiming lordship over the .local domain. In my opinion, mdns is
breaking DNS, and telnet'ing to a .local machine is more important to
me that Rendezvous. If it is a requirement to reserve the .local tld,
then Apple should get on the ball and write the draft and get it turned
into an RFC
-josh
On Monday, Jun 9, 2003, at 13:26 US/Pacific, Peter John Hill wrote:
Hello all,
We (Carnegie Mellon) have re-ip'd all of our access points and
wireless switches to use RFC 1918 addresses and have changed their
dns domain from sw.cmu.net to sw.cmu.local
Now we are seeing the following:
[TITAN:~] phill% host mg-e-wl-a.sw.cmu.local
mg-e-wl-a.sw.cmu.local has address 172.18.65.152
[TITAN:~] phill% telnet mg-e-wl-a.sw.cmu.local
mg-e-wl-a.sw.cmu.local: No address associated with nodename
Looking into a packet dump while telnetting shows my machine trying
to find the host via multicast dns.
Ideally there would be something like
/etc/hosts.conf
order bind,mdns,local
So, do I need to dig my hosts and telnet to them by IP?
Peter Hill
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.