On Mon, September 4, 2017 14:22, Mark Andrews wrote: > > In message <c0c73dab49c6452c616c86656704ecd0.1504518...@squirrel.mail>, > "Walter H." writes: >> where there anyone who said: "don't use it", 15 years ago? > > Yes. There were lots that discourage the use of .local, lan, > .corp etc. Just becaue you didn't hear from them doesn't mean > they weren't out there.
a discourage is not a "don't use" :-) >> > 'home.arpa' is in the process of being registered so that it >> > can be used safely in the environment it is designed to be used in. >> >> yes, but commonly for residental networks, not company/enterprise >> networks, >> they want/need something shorter like ".corp", ".lan", ".local", ... > > Want maybe, need absolutely not. question: why isn't this the answer of a car dealer? > Everyone was told to register the domain you want to use, there was > no exception for active directory. not really, at those days only a few TLDs where possible, the many TLDs came some years later ... by the way: where is the problem with .home or .corp? I ask this, because at my hoster I pre-reserved my "local domain" - a .home, that I have used for many years several zears ago and nothing happened ... > IPv6 would have been deployed a lot sooner. :-) not really, my ISP is still IPv4 only ..., my IPv6 connectivity is a HE-tunnel ... and the brand new OS from Microsoft still has the bugs inside: TEREDO, ... which I had to deactivate first, before it is usable with IPv6 at all ... > Except such systems exist. Go look at what a Mac does. ping for > test.local and look and port 5353 traffic and compare it to port 53 > traffic. I know, this RFC was written by Apple; no Apple no problem, I would say :-) _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
