Re: mirroring domains



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.



.



Relevant Pages

  • Re: DNS stopped forwarding
    ... > One step in our troubleshooting was to point different DNS ... > servers on their network. ... but I support another SBS system that uses the same ISP and DNS ... servers and it still works fine. ...
    (microsoft.public.windows.server.sbs)
  • Re: Help SMPT Errors
    ... FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your ... it may mean that your DNS servers did not respond fast enough). ... INFO NS records at parent servers Your NS records at the parent servers ... PASS Parent nameservers have your nameservers listed OK. ...
    (microsoft.public.exchange.admin)
  • Re: Windows 2000 logon process
    ... Paul Williams ... when clients are accessing the GPO stored in SYSVOL during logon. ... PW>> Sound's like - that's a combination of DNS and Dfs client pointing ... Global Catalogue servers? ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... on 2 servers out of 4 DNS servers. ... DNS and 2003 DNS and how to set up Conditional Forwarding. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Howto refresh IIS 6 Application pool identity credential info
    ... You already have 80% of the work setup (DNS Aliases and HostHeaders) on the ... domain accounts (one for each layer) should be sufficient. ... The Application Servers are load balanced clustered, ... as the account name and SPN alias is correctly defined on both nodes. ...
    (microsoft.public.inetserver.iis.security)

Loading