Greetings,
Environment:
AD 03 controllers at different sites, talking to each other via IPSEC VPN tunnels. Each site is on a different subnet.
I am considering establishing a standard naming convention for the AD boxes and other servers, such that the machine name would be the same e.g. AD, but the dns address would be distinguished via 3rd level dns domains.
For example, the AD box in our Bangkok office would be
ad.bkk.abcde.com and the AD box in NY would be
ad.nyc.abcde.com.
This would make our naming more intuitive. However, I am concerned that with the machine names being identical, we will have netbios name conflicts.
Should we just use a different naming convention and make sure the machine names are different, or am I worrying too much.
thanks.
Environment:
AD 03 controllers at different sites, talking to each other via IPSEC VPN tunnels. Each site is on a different subnet.
I am considering establishing a standard naming convention for the AD boxes and other servers, such that the machine name would be the same e.g. AD, but the dns address would be distinguished via 3rd level dns domains.
For example, the AD box in our Bangkok office would be
ad.bkk.abcde.com and the AD box in NY would be
ad.nyc.abcde.com.
This would make our naming more intuitive. However, I am concerned that with the machine names being identical, we will have netbios name conflicts.
Should we just use a different naming convention and make sure the machine names are different, or am I worrying too much.
thanks.