Re: mirroring domains
- From: "Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 May 2006 13:05:09 -0700
I agree with Jorge that this is sort of asking for problems - especially
when troubleshooting. I do believe that if you set all computers to a p-node
type of resolution and make sure they are using only the DNS and WINS
servers for the domain they are members of you wouldn't have a problem. If,
however, at any time you require NetBIOS name resolution accross the
domains, you'll be in trouble. You might see about coming up with some sort
of standard suffix for servers in the new domain that could distinguish one
from the other when NetBIOS resolution is required (Server01 -
Server01-D2)...
....kurt
"richard" <r_blears@xxxxxxxxxxx> wrote in message
news:1147360117.363409.179170@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am probably being really dumb but....
I have created a new domain dev.local, production domain is prod.local,
I have created a dc obviously dc.dev.local, however, I have been asked
to create machines within this doiman that are the same name a servers
in our production domain. Now that shouldn't be a problem, but both
domains are on the same subnet.
Whilst the dc is providing dns and wins services, I know I will not
have an issue with dns, I am more concerned with netbios.
Assuming I build the machines with wins and dns pointing at the new dc,
will i have any issues that i should watchout for?
can anyone see any issues that i might come across for client machines
wishing to connect to the dev.local doamin and resolving names
correctly. I know that I will need to configure ip details manually for
wins and dns, but should that be it?
Hope you can help.
Thanks
Richard.
.
- References:
- mirroring domains
- From: richard
- mirroring domains
- Prev by Date: Re: mirroring domains
- Next by Date: LDAP binding weirdness between 2000 and 2003
- Previous by thread: Re: mirroring domains
- Next by thread: LDAP binding weirdness between 2000 and 2003
- Index(es):
Relevant Pages
|
Loading