> 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 TLD so it's NOT reserved by any means, it's just being used by someone That said, I prefer avoiding the use of "special" TLDs, if you own the domain "example.com" you may just use it for your public needs and for your private ones, using the same domain on your "LAN" just means setting up a "split horizon" DNS and won't take too much, then, if you don't want or can't setup a "split horizon" DNS you may just go on and let the DNS work as it was designed; in such a case you may just use (e.g.) "priv.example.com" as your private domain and still avoid "collisions" since you'll own the "example.com" domain and nobody else will be able to use it :) As for ASSP, I think that the "private domain" is a non existing problem, see, let's say your ASSP full name is assp.example.com now, all you'll need to do is setting it up so that "assp.example.com" will ALSO be the locally managed domain, so, messages sent to the email interface will be addressed to [email protected] no fuss, no muss and... no collisions :) ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
