FQDN

Everything I read tells me that a 2003 server should be setup with a FQDN.

1) What if it's just as a member of a workgroup, never to access the internet?

2) What if it's a member of a workgroup that is then setup as a Domain Name
Server.

3) Would the computer name "server1.local" satisfy DNS and stop event log
errors.

4) If the 2003 server already has a computer name, can I add a SUFFIX
without upsetting access to the existing workgroup?

Regards to all,
Wambat

Wambat пишет:
> Everything I read tells me that a 2003 server should be setup with a FQDN.
>
> 1) What if it's just as a member of a workgroup, never to access the internet?
If you don't use DNS in your environment, you can leave DNS client
unconfigured.

>
> 2) What if it's a member of a workgroup that is then setup as a Domain Name
> Server.
You will have some problems, because DNS server will assume, that uor
computer placed in root domain (so it has no suffix). When you'll
install DNS server it will automatically create "." zone and "A" record
in this zone for your server, then, when you create your zone it will
has "NS" record pointing to that "A" record. And, of course, your server
will be unresolvable from Internet.

>
> 3) Would the computer name "server1.local" satisfy DNS and stop event log
> errors.
Yes.

>
> 4) If the 2003 server already has a computer name, can I add a SUFFIX
> without upsetting access to the existing workgroup?
Yes. Workgroup comes from NetBIOS namespace and it has no interference
with Domain Name System.




--
With best regards
Nickolay Domukhovsky, MCSA

"Wambat" <(E-Mail Removed)> wrote in message
news:654ACC83-8081-4220-802D-(E-Mail Removed)...
> Everything I read tells me that a 2003 server should be setup with a FQDN.

What in the world are you reading? :-)

> 1) What if it's just as a member of a workgroup, never to access the internet?

No FQDN

> 2) What if it's a member of a workgroup that is then setup as a Domain
> Name Server.

No,...and there is no reason to set it up as a DNS Server either.

> 3) Would the computer name "server1.local" satisfy DNS and stop event log
> errors.

No. That is an invalid machine name.

> 4) If the 2003 server already has a computer name, can I add a SUFFIX
> without upsetting access to the existing workgroup?

There is no suffix in a workgroup.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------

Thanks for the replies.. I got no idea why I was so confused. The light has
come on and I understand.
Wambat
"Wambat" <(E-Mail Removed)> wrote in message
news:654ACC83-8081-4220-802D-(E-Mail Removed)...
> Everything I read tells me that a 2003 server should be setup with a FQDN.
>
> 1) What if it's just as a member of a workgroup, never to access the
internet?
>
> 2) What if it's a member of a workgroup that is then setup as a Domain
Name
> Server.
>
> 3) Would the computer name "server1.local" satisfy DNS and stop event log
> errors.
>
> 4) If the 2003 server already has a computer name, can I add a SUFFIX
> without upsetting access to the existing workgroup?
>
> Regards to all,
> Wambat
>