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
<(E-Mail Removed)> wrote in message
news:a1658e57-d804-4c5c-8918-(E-Mail Removed)...
> 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