Developer Forum

The server will not be a web server, only a local area network server.
Just curios.
Thanks.

I guess you can name it anything you wish, although it seems like you're
inviting some kind of unanticipated problem (that doesn't occur to me
offhand) if you use one of those. However, IMO you should use something
besides .com. See this KB:

The Domain Name System name recommendations for Small Business Server 2000
and Windows Small Business Server 2003
http://www.yqcomputer.com/

Windows update, WSUS, Activations?, anything else that would normally get
forwarded out (or root hints)unresolved by local DNS would (likely) fail.






--
/kj

Hell, you can name it anything you want. That doesn't mean it's a good idea.
You're going to run into name resolution problems for your clients/servers.
Avoid real domain names or TLDs - stick with .local or .lan. You might also
keep it somewhat generic, e.g., office.lan.

I'm not sure why you would want to do this but if your server will NEVER
connect to the outside world you can name it whatever you want.

--
Claus

Why would you desire to do so?

In article < XXXX@XXXXX.COM >,
XXXX@XXXXX.COM says...

If you name it anything that is already used, you best not install DNS
on it.

A LONG TIME AGO, one of my first mistakes was setting up DNS, before SBS
was even around, and I called my network Stormy.com, figuring it fit as
it was a development network. Well, I started watching my firewall logs
and found some 600 connections an hour, to what I misread as inbound, of
someone trying to hammer my DNS service (which I didn't expose).

As it turns out, my DNS service was trying to replicate with the real
stormy.com and was hammering their DNS server....

That was a long time ago....

It's best to NEVER name your internal DNS anything that could be public
in name - use microsoft.lan or microsoft.local, but never any TLD name.

If you want microsoft.com to resolve to your internal network, from your
internal network, then create a DNS entry for it.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
XXXX@XXXXX.COM (remove 999 for proper email address)

Why not call it i-troll.com?
--
:-)

ROTFLMAO

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC

Oh boy.

Reminds of my first brilliant IP selection in the early 90's (90.0.0.x).
I could never figure out how a a machine with a French name could show
in my browse list.

:-)

reminds me of all those SCO engineers, who took what was written in the book
literally.

SCO Unix literature uses a particular IP range in the examples. Older
literature doesn't even mention 'private IP space'. 9 out of 10 SCO systems
I encounter cannot access a particular public subnet.

Actually, that 9x.y.z.a range sounds familiar. You an ex-SCO man? (further,
I think it was 96.whatever, but maybe memory is fooling me again. Maybe
you're not an SCO man)