Re: private network domain names
"Jonathan Hall" <[email protected]> Thu, 1 May 2003 21:13:03 -0500
| Newsgroups | gmane.org.user-groups.aclug.linux-help |
|---|---|
| Message-ID | <000701c31051$c918d8b0$11056644@tirian> |
I don't know if it's "standard"... but what I use for my private network segment is *.private.flimzy.com. flimzy.com is a true domain, and I use it for many things, but private.flimzy.com is not seen by the outside world. I have one "private" DNS server that hosts that zone, and shares it with nobody except local hosts (192.168.x.x). I've also seen people use *.local, etc. As for what is the standard? I have no idea... I suspect there isn't one. ----- Original Message ----- From: "Tom Hull" <[email protected]> To: <[email protected]> Sent: Thursday, May 01, 2003 9:04 PM Subject: [linux-help] private network domain names > If I want to set up a private network I know I can use an address > reserved for such purposes, e.g. 192.168.1/24. However, is there > any standard or convention for deciding what domain name to use > for that network? > > Obviously, the domain name does not need to be registered or > externally resolved, but all sorts of local software (e.g., mail > software) assumes or demands that you have a domain name. And > obviously the domain name, like the network address, must be > something that you will never want to resolve into an external > address. So it would make sense to reserve, say, a top level > domain for private networks, but I've never seen anything that > makes such a reservation. E.g., RFC 1918 says nothing about > domain names. > > -- > /* > * Tom Hull * thull2 at cox.net * http://www.tomhull.com/ > */ > > -- This is the [email protected] list. To unsubscribe, > visit http://www.complete.org/cgi-bin/listargate-aclug.cgi > > -- This is the [email protected] list. To unsubscribe, visit http://www.complete.org/cgi-bin/listargate-aclug.cgi