> 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" the domain and have (e.g.) uk.lan.example.com de.lan.example.com ... or, willing do further "drill down" one may even have london.uk.lan.example.com bristol.uk.lan.example.com ... the advantage of such an approach is that you'll never have "collisions" since you are the one owning the parent domain; also, if queries will "spill out" from your network perimeter, the root-servers will drive them back to your AUTH nameservers :) - then, to avoid any external one to query whatever private host you may either setup views (as you did) or just setup some DNS handling the "lan.example.com" zone and configure the "public" one to delegate such a zone to those DNS; these will be sitting on private (or filtered) IPs so that queries from the external will never reach them :) ------------------------------------------------------------------------------ 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
