DNS setup

  • Thread starter Thread starter taaper
  • Start date Start date
T

taaper

Hello everyone,
I've been through 15 pages here and haven't seen my issue,
maybe someone could advise. New W2K Server (will be the
only DC); it will have 5 users with no connection to the
outside world. Customer (now with a NT domain, working
well) wants AD (I think the salesman pushed it to sell the
product - new server; new OS). They want to use the
FQDN: "computer.lan" .
In setting up DNS should I (can I) set it up as;
1) first off, is ".lan" - acceptable?
2) Computer.lan. - a period at the end of lan?

Any assistance is greatly appreciated....
Thanks,
taaper
 
In
taaper said:
Hello everyone,
I've been through 15 pages here and haven't seen my issue,
maybe someone could advise. New W2K Server (will be the
only DC); it will have 5 users with no connection to the
outside world. Customer (now with a NT domain, working
well) wants AD (I think the salesman pushed it to sell the
product - new server; new OS). They want to use the
FQDN: "computer.lan" .
In setting up DNS should I (can I) set it up as;
1) first off, is ".lan" - acceptable?
2) Computer.lan. - a period at the end of lan?

Any assistance is greatly appreciated....
Thanks,
taaper
Click to expand...

Not a good idea, lan would be a single label domain name which is not
acceptable by Win2kSP4, XP Pro, and Win2k3 members of the domain. you have
to add a registry entry on all these machines. "domain.lan" would be OK.
 
Thanks,
will start working on getting them to use a conventional
FQDN
Regards,
taaper
-----Original Message-----
In taaper <[email protected]> posted a question
Then Kevin replied below:

Not a good idea, lan would be a single label domain name which is not
acceptable by Win2kSP4, XP Pro, and Win2k3 members of the domain. you have
to add a registry entry on all these
Click to expand...
machines. "domain.lan" would be OK.
 
Back
Top