Active Directory DNS name

  • Thread starter Thread starter tst
  • Start date Start date
T

tst

We are planning to upgrade NT PDC to windows 2000 AD. Our
primary DNS server is in Linux. E.g, Linux DNS name is
abc.com.sg and NT domain name is xyz. So for the AD DNS
(FQDN) name, we should put abc.com.sg or xyz.abc.com.sg?
Or we can put FQDN as abc.com.sg but NETBIOS name remains
in xyz? Another question is our users are using Winnt
workstation, Windows 2000 professional and Windows XP
professional. After the upgrade, they should login to old
NT domain name or AD DNS name? Please advise.
 
| We are planning to upgrade NT PDC to windows 2000 AD. Our
| primary DNS server is in Linux. E.g, Linux DNS name is
| abc.com.sg and NT domain name is xyz. So for the AD DNS
| (FQDN) name, we should put abc.com.sg or xyz.abc.com.sg?
| Or we can put FQDN as abc.com.sg but NETBIOS name remains
| in xyz? Another question is our users are using Winnt
| workstation, Windows 2000 professional and Windows XP
| professional. After the upgrade, they should login to old
| NT domain name or AD DNS name? Please advise.
|

The FQDN for the AD domain can be whatever you want it to be. The key is,
the DNS server need s to be authoritative for that domain. Therefore, the
can set it to be xyz.com and leave the netbios name as xyz. For your
clients, when they logon they will pick from the list (in a single domain
the list will jsut be local machine and domain). The domain will be listed
with the NetBios name. Using the above, this will still be XYZ.

Chad A. Lacy
Windows 2000 Directory Services

==================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks for the reply. What if we want to set our client's
full computer name as "computerA.abc.com.sg", is it
correct to say that the FQDN name must be set as
abc.com.sg as well?
 
---
| Thanks for the reply. What if we want to set our client's
| full computer name as "computerA.abc.com.sg", is it
| correct to say that the FQDN name must be set as
| abc.com.sg as well?

Yes, that is exactly correct. The client machine will inherit the FQDN of
whatever domain they are joined.

Chad A. Lacy
Windows 2000 Directory Services

==================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
| We are planning to upgrade NT PDC to windows 2000 AD. Our
| primary DNS server is in Linux. E.g, Linux DNS name is
| abc.com.sg and NT domain name is xyz. So for the AD DNS
| (FQDN) name, we should put abc.com.sg or xyz.abc.com.sg?
| Or we can put FQDN as abc.com.sg but NETBIOS name remains
| in xyz? Another question is our users are using Winnt
| workstation, Windows 2000 professional and Windows XP
| professional. After the upgrade, they should login to old
| NT domain name or AD DNS name? Please advise.
|

The FQDN for the AD domain can be whatever you want it to be.
The key is, the DNS server need s to be authoritative for that
domain. Therefore, the can set it to be xyz.com and leave the
netbios name as xyz. For your clients, when they logon they will
pick from the list (in a single domain the list will jsut be local machine
and domain). The domain will be listed with the NetBios name.
Using the above, this will still be XYZ.
Click to expand...
Hi Chad,

As I understand it, a FQDN only applies to *hosts*.

http://www.webopedia.com/TERM/F/FQDN.html

Are you saying that this usage has been extended to AD Domains too?

Cheers,

Cliff

(MVP)
 
Back
Top