Subject: Re: "good" domain name for internal network
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Daniel R. Killoran,Ph.D. <drkilloran@speakeasy.net>
List: netbsd-help
Date: 06/18/2003 12:12:17
Stephane Bortzmeyer wrote:
>On Mon, Jun 02, 2003 at 01:09:13PM +0900,
> henry nelson <netb@irm.nara.kindai.ac.jp> wrote
> a message of 14 lines which said:
>
> > I'd like to use domain names to identify what/where the network is, but
>> I'd rather not use things like .edu or .ac.xx (xx = some country's
>> abbreviation). Are there suffixes to domain names that are reserved for
>> internal networks
>
>Partially, see RFC 2606 :
>
> To safely satisfy these needs, four domain names are reserved as
> listed and described below.
>
> .test
> .example
> .invalid
> .localhost
>
> ".test" is recommended for use in testing of current or new DNS
> related code.
>
> ".example" is recommended for use in documentation or as examples.
>
> ".invalid" is intended for use in online construction of domain
> names that are sure to be invalid and which it is obvious at a
> glance are invalid.
>
> The ".localhost" TLD has traditionally been statically defined in
> host DNS implementations as having an A record pointing to the
> loop back IP address and is reserved for such use. Any other use
> would conflict with widely deployed code which assumes this use.
I usually use ".lan" - that makes it pretty obvious.
Dan Killoran