[lug] dns for non Internet visible network

Lee Woodworth blug-mail at duboulder.com
Fri Dec 31 12:21:19 MST 2004

The only issue I can think of when using a fake TLD is the operation of 
software that expects correct DNS setups. An example might be spam 
filtering systems.

Its easy enough to set up a subdomain of your public domain. The 
subdomain doesn't have to be publicly visible.

Hugh Brown wrote:
> What's the "best practice" 
for setting up dns for a group of systems
> that aren't addressable from the Internet?  Do people use .dom endings
> or do they just extend the domains that they own?
> For example:
> I have a lot of machines at home and I don't want to manage
> the /etc/hosts file (or equivalent on other OSes) on all of them.  I'm
> going to set up dns on one of the boxes and I'm wondering what the
> preferred method is for domain naming esp. since this dns server won't
> be accessible by any Internet hosts.
> It seems like I could just call the domain myhomedomain.blah and set up
> the forward and reverse zones for it (on a reserved non-routed ip
> range).  It seems like I could also use one of the domains that I have
> registered and do that.
> Any experiences?
> Hugh

More information about the LUG mailing list