Mark Minasi's Tech Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 2      Prev   1   2
jsclmedave

Administrator
Registered:
Posts: 506
Reply with quote  #16 
Quote:
Originally Posted by JamesNT
Thank, bit.  From what you are saying we are all set.  Our AD is small (a dozen users and a dozen servers/workstations) and changes are seldom. 

One last question:  When my coworkers went to customer site and installed the third DC, they did not set any DNS settings.  At all.  Just pointed the third DC to DC1 and DC2 but not the other way around.  How much trouble are we in?  It's been that way for a few weeks now.  Should we set DNS or get rid of the DC3?

JamesNT


When you say "installed a third DC" you mean that promoted it within your Domain correct?

They need to be able to communicate to the other DC's so setup DNS accordingly.

Are these RODCs' or full blown?

Are they on the same Subnet?

Can you see them ALL in Sites & Services?

__________________
Tim Bolton @jsclmedave
Email: [string](0..20|%{[char][int](32+('527377347976847978324785847679797514357977').substring(($_*2),2))}) -replace ' '  

New to the forum? Please Read this
0
Wobble_Wibble

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 45
Reply with quote  #17 
Get a person of responsibility to add the DNS of another server and visa versa.
You'll be grand, once you get connected, sort the other issues.

__________________
Press any key....
Yes, any key....
OK, try the space bar.
0
anthony

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 56
Reply with quote  #18 
If it's a small environment, why do you have 3 domain controllers? Just curious.
__________________
If Chewbacca lives on Endor - You must acquit!
0
JamesNT

Senior Member
Registered:
Posts: 147
Reply with quote  #19 
Anthony,

Redundancy.  Uptime is important here.

JamesNT

__________________
I miss Windows NT 4.0 Service Pack 4.
0
JamesNT

Senior Member
Registered:
Posts: 147
Reply with quote  #20 
Tim,

All full blown DC's.

The third DC was promoted.

Everyone is on the same subnet.

Don't know.  I wasn't the person who set the thing up.  If I was, we wouldn't be having this problem.

JamesNT

__________________
I miss Windows NT 4.0 Service Pack 4.
0
dennis-360ict

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 94
Reply with quote  #21 
Ive had some problems using the first dns entry to point to another dc. This was on win08r2 virtual dc's that were on very fast (ssd) storage. The problem was it started so fast, the dns could not keep up and gave me errors in the eventlog. This resolved itself after a while when everything else started, but i didnt like those errors while starting. I resolved this by using 127.0.0.1 for the first dns entry and using the second dns entry for theother dc. Ive stuck with this and been doing it ever since. Just my bit anyway.
__________________
-----
Home is where is sleep
360ict.nl/blog
thegood.cloud
0
pcmeiners

Still Checking the Forum Out
Registered:
Posts: 2
Reply with quote  #22 
In addition, does not matter how many DNS servers you have or their order if workstations are redirected to a rouge server by malware....
For added security, at the network perimeter firewall, I block all work stations/servers DNS access, except for the internal DNS servers. All machines/devices needing DNS therefore must go through the internal DNS servers with forwarding to known legit external servers.

0
Phil-n-JaxFL

Avatar / Picture

Grumpy Old Men
Registered:
Posts: 87
Reply with quote  #23 
JamesNT, I would recommend keeping DC3, since it is at the site, and I would set the DNS: Pri - DC1, Sec - DC2, Ter - DC3, but you should not be in any trouble, providing your replication is working properly. As a couple of people have said on here, the Island issue hasn't reared its ugly head in years.
__________________
Phil
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.