Stephen Brown on Thu, 7 Nov 2002 21:30:08 +0100 |
Jeff Abrahamson wrote: (And clearly, to head off comment, the public purple.com DNS can't talk about dog.purple.com, since dog has a 192.168 address...) What I do is the same as jeff mentioned, have your internal boxes with unique names in the external domain. It doesn't matter that fungi.blinkylight.net is a 192.168 address since you can't get to it except inside my network. But (www|ns|mx).blinkylight.net all properly resolve to a real external address. Things work naturally inside the network, and you can even set up a normal caching DNS server inside that will continue to server purple.com addresses if your net connection goes away. Another option would be to use a subdomain (home.purple.com) for all of your in-house boxen, possibly even CNAME dog.purple.com to dog.house.purple.com I messed around with the internal/external view of domains with bind 9 but didn't find it worth the trouble for my setup. steve _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|