Re: Intranet Naming Standard?
From: Daniel R. Tobias (dan_at_tobias.name)
Date: 10/15/04
- Next message: William Stacey [MVP]: "Re: Query for User?"
- Previous message: Herb Martin: "Re: Root Hints or forwarders?"
- In reply to: Dan P: "Re: Intranet Naming Standard?"
- Messages sorted by: [ date ] [ thread ]
Date: 15 Oct 2004 13:29:20 -0700
"Dan P" <nospamdan@pancamo.com> wrote in message news:<#SomAC8qEHA.2796@tk2msftngp13.phx.gbl>...
> A. Use *.company.com for all non windows devices, URL names, etc..
> Ex. portia.company.com, http://mobius.company.com
>
> B. Use corp.company.com for all windows server naming
That seems most logically consistent, putting all your stuff under the
same domain, in the .com TLD (appropriate if you're a for-profit
business).
Does the company actually own the company.com domain? It's a bad idea
to use (even on an internal basis) addresses that are actually in a
domain that somebody else owns (or that is unregistered now and could
be taken by somebody else in the future), as this may cause addresses
to conflict with others' addresses on the Internet. Even disconnected
intranets are sometimes connected to the outside network and such
conflicts become a problem later.
> 2. Reclaim company.net (Currently we cannot use company.net due to Active
> Directory configurations)
Is your company a network infrastructure provider? If not, the .net
domain doesn't make logical sense.
As with company.com, does the company actually own company.net?
> 3. New INTERNAL Top Level Domains (TLDs)
Potentially a bad idea, since the TLDs you create might eventually be
matched by actual new TLDs added into the Internet, causing addressing
conflicts.
[top-posted fullquote snipped; don't top post!]
-- Dan
- Next message: William Stacey [MVP]: "Re: Query for User?"
- Previous message: Herb Martin: "Re: Root Hints or forwarders?"
- In reply to: Dan P: "Re: Intranet Naming Standard?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|