FQDN as .com versus .local - Change?

We setup a new Windows 2003 Server as a DC, File Server & DNS Server.
We have not added any user or computer accounts yet. We meant to
create a companyname.local FQDN but inadvertantly left it as
companyname.com

This server is on a small network (less than 5 PCs) with no intention
of having an internal website. Very basic use.

Does anyone see a need to change the FQDN?

If so, how do we do it?

Thanks

Since you are "no intention of having an internal website", you can keep
..com. But I would change to .local just in a case I would need the web
site.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
<[email protected]> wrote in message
news:a1658e57-d804-4c5c-8918-79204f0767d8@k13g2000hse.googlegroups.com...
> We setup a new Windows 2003 Server as a DC, File Server & DNS Server.
> We have not added any user or computer accounts yet. We meant to
> create a companyname.local FQDN but inadvertantly left it as
> companyname.com
>
> This server is on a small network (less than 5 PCs) with no intention
> of having an internal website. Very basic use.
>
> Does anyone see a need to change the FQDN?
>
> If so, how do we do it?
>
> Thanks

<[email protected]> wrote in message
news:a1658e57-d804-4c5c-8918-79204f0767d8@k13g2000hse.googlegroups.com...
> We setup a new Windows 2003 Server as a DC, File Server & DNS Server.
> We have not added any user or computer accounts yet. We meant to
> create a companyname.local FQDN but inadvertantly left it as
> companyname.com
>
> This server is on a small network (less than 5 PCs) with no intention
> of having an internal website. Very basic use.
>
> Does anyone see a need to change the FQDN?

It can limit what you do with DNS (externally on the web). For example if
you wanted to set up an internet name ftp.companyname.com this would cause
you grief if one of your pcs were called "ftp" because its FQDN is
ftp.companyname.com. (Ditto if you ever wanted to redirect all subdomains on
the net, so *.companyname.com.) This may sound unlikely but it can be a real
pain if you hit it as a problem. I'd strongly suggest you start over and go
for .local.

> If so, how do we do it?

Whilst Microsoft do publish a domain rename tool, unless they've updated it
it used to appear as just a long list of instructions with plenty of scope
for things to go wrong. I've not done it for a long time but I think the
simplest is a case of removing active directory and then reinstalling AD but
with the new name.

Having been there and suffered the long term consequences I'd advise taking
the hit now and move to .local.
--
Brian Cryer
www.cryer.co.uk/brian