DC with 2 NICs and DNS resolving in the different subnets


have dcs 2 nics on each dc. have 2 subnets. 192.168.0.1/24 (subnet 1 ) , 192.168.0.10/24 (subnet 2)

first nic on each dc looks to  subnet 1 , second nic on each dc looks subnet 2

client makes dns request dc's dns , got respond dns contains 2 ips subnet 1 , subnet 2

example client asks dns about  dc's ip , gets ips subnet 1 , subnet 2. because  routing not exist between subnet 1 , subnet 2 sometime when client tries use ip subnet connections/operations failed.

question is exist way how setup dns servers return answer ip contains ip correct subnet. example if dns request subnet 2 clients should ip subnet 2 .

dns ms dns server.


dns configuration best practice on dc , clients/member servers:

-->>multihoming domain controllers not recommended, results in multiple problems.
------------------------------------
1. domain controllers should not multi-homed
2. being vpn server , running rras makes multi-homed.
3. dns itself, better on single homed machine.
4. domain controllers pdc role automatically domain master browser. master browsers should not multi-homed

272294 - active directory communication fails on multihomed domain controllers http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

191611 - symptoms of multihomed browsers
http://support.microsoft.com/default.aspx?scid=kb;en-us;191611

-->>dns configuration on domain controller:
------------------------------------------
1. each dc / dns server points private ip address primary dns server , other internal/remote dns servers secondary dns in tcp/ip property.
2. each dc has 1 ip address , 1 network adapter enabled (disable unused nics).
3. if multiple nics (enabled , disabled) present on server, make sure active nic should on top in nic binding.
4. contact isp , valid dns ips them , add in forwarders, not set public dns server in tcp/ip setting of dc.

-->> ip configuration on clients , member servers:
-----------------------------------
1. each workstation/member server should point local dns server primary dns , other remote dns servers secondary.
2. not set public dns server in tcp/ip setting of client/member server.

once done above, run "ipconfig /flushdns & ipconfig /registerdns", restart dns server , netlogon service on each dc.


best regards,

sandesh dubey.

mcse|mcsa:messaging|mcts|mcitp:enterprise adminitrator | blog

disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...