Complete.Org: Mailing Lists: Archives: linux-help: May 2003:
[linux-help] Re: private network domain names
Home

[linux-help] Re: private network domain names

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: <linux-help@xxxxxxxxx>
Subject: [linux-help] Re: private network domain names
From: "Dale W Hodge" <dwh@xxxxxxxxxxxxxxxx>
Date: Fri, 2 May 2003 12:26:30 -0500
Reply-to: linux-help@xxxxxxxxx


> -----Original Message-----
> From: linux-help-bounce@xxxxxxxxx [mailto:linux-help-bounce@xxxxxxxxx]On
> Behalf Of Jonathan Hall
> Sent: Thursday, May 01, 2003 9:13 PM
> To: linux-help@xxxxxxxxx
> Subject: [linux-help] Re: private network domain names
>
>
> 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.

All you can be sure of is what ICANN/IANA has currently assigned.
http://www.icann.org/tlds/ There is nothing that says any TLD (top level
domain) can't become active at any time.  My guess for safe bets would be
.local or .home  I would also guess that .<'lastname'> would be safe for the
forseable future.

--dwh

---
Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
Vice Chairman & Secretary - info@xxxxxxxxx
Air Capital Linux User's Group  (ACLUG)
www.aclug.org
---






-- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
visit http://www.complete.org/cgi-bin/listargate-aclug.cgi


[Prev in Thread] Current Thread [Next in Thread]