You can do that. My own internal DNS uses .int.
So, for example, my laptop is katamari.225swan.int
DHSinclair wrote:
OKay. I recall the r2l read thing. So, I could do something like:
oaktree.local (domain)
and end up with my clients on the LAN as:
ofc.oaktree.local (client pc)
gam.oaktree.local (client pc)
gxp.oaktree.local (client pc)
lib.oaktree.local (client pc)
srv.oaktree.local (server)
2070n.oaktree.local (printer)
blkhol.oaktree.local (router)
Close? I will go read your sends also...... :)
Best,
Duncan
At 16:43 11/03/2007 -0700, you wrote:
Remember domain name hierarchy works right to left.
".com" is a top level domain
controlled by verisign, MS leases Microsoft.com
sub-domain from verisign,
search.Microsoft.com and other *.Microsoft.com domains
are controlled by
Microsoft.com.
http://en.wikipedia.org/wiki/.com
For non-internet routable AKA "private" domains I'd
follow the MS suggestion
".local" because there is no such top level domain on
the internet. I.E
"mydomain.local" domain with machines named like
"server.mydomain.local",
"laptop.mydomain.local", etc....
http://support.microsoft.com/kb/296250
"Make the name a private domain name that is used for
name resolution on the
internal Small Business Server network. This name is
usually configured with the
first-level domain of .local. At the present time, the
.local domain name is not
registered on the Internet."
DHSinclair wrote:
> Are there any entry level links that explain do's
and don't's when
> trying to create/formulate a proper id/value/name
for a private domain?
>
> From the last several months I get the idea that a
domain name is
> something like:
>
> word1-dot-word2-dot-word3
>
> IIRC, the "word3", in a commercial space, could be
something like .com,
> .gov, .net, as I've seen so far. (do have the RFC
and/or IANA docs that
> show listings). Wondering.
> Best,
> Duncan
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
