> I always set my local domains up as lan.example.com,
> with nameserver views to prevent anyone external ever
> knowing about the sub-domain.
Yes, that's one of the methods I wrote about in my other
email and it's pretty flexible too, see, in case one has
multiple offices, it's easy to "expand"
I always set my local domains up as lan.example.com, with nameserver
views to prevent anyone external ever knowing about the sub-domain.
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development K
> Ok - I'll rephrase. Since Apple/Zeroconf/Avahi/mDNS/whoever
> else blatantly stole the ".local" domain suffix, in express violation
> of previous standard practices (if not published standards or RFC's)
> preached by various prophets including followers of the mighty Church
... of the swimming
On 8/4/2010 1:55 AM, GrayHat wrote:
>> Previously I was taught to use .local for my LAN domain suffixes.
>> But with the new auto-configuration technologies like mDNS and
>> Avahi .local has now become a reserved namespace.
>>
> Hm... first of all it's NOT reserved; no DNS server (try running
> Previously I was taught to use .local for my LAN domain suffixes.
> But with the new auto-configuration technologies like mDNS and
> Avahi .local has now become a reserved namespace.
Hm... first of all it's NOT reserved; no DNS server (try running
a query like "dig local NS") is serving that T
Daniel L. Miller wrote:
> Previously I was taught to use .local for my LAN domain suffixes.
> But with the new auto-configuration technologies like mDNS and Avahi
> .local has now become a reserved namespace.
>
> Is there a designated suffix for non-public use? Preferably
> something reserved by R
Previously I was taught to use .local for my LAN domain suffixes. But
with the new auto-configuration technologies like mDNS and Avahi .local
has now become a reserved namespace.
Is there a designated suffix for non-public use? Preferably something
reserved by RFC so it won't get stepped on
