DNS not updating across domains
we changed name of our wsus server , name did not replicate across domains. have 1 domain on server 2008 , other on windows 2003 active directory integrated. problem new name not updating 2003 domain.
1st domain prod.net 2 dc's dc1 , dc2 on 2008
and 2 dns zones
zone 1: prod.net
zone 2 prod.web.net
2nd domain prod-web.net 2 dcs wdc1 , wdc2 on 2003
and 2 dns zones
zone 1:prod.net
zone 2:web.net
the name change on prod.net on 2008 correct , prod.net on 2003 incorrect. there 1 way trust between domains
hi,
we changed name of our wsus server , name did not replicate across domains.?
understood comments wsus server's new name registered in dns server in prod.net domain not in prod-web.net .
next
the name change on prod.net on 2008 correct , prod.net on 2003 incorrect. there 1 way trust between domains.
resolve issue, check required ports open on firewall
see ports requirement ad.
http://technet.microsoft.com/en-us/library/dd772723(ws.10).aspx
in addition,
active directory replication on firewalls
http://social.technet.microsoft.com/wiki/contents/articles/active-directory-replication-over-firewalls.aspx
you may use portqryv2.exe, command-line utility can use troubleshoot tcp/ip connectivity issues.
http://www.microsoft.com/download/en/details.aspx?id=17148
portqryui - user interface portqry command line port scanner
http://www.microsoft.com/download/en/details.aspx?id=24009
also ensure below configuration dc , clients:
-->>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
-->> ip configuration on domain controller:
------------------------------------------
1. each dc / dns server points private ip address primary dns server , other internal/remote dns servers secondary ones
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 ws.
once done above, run "ipconfig /flushdns & ipconfig /registerdns", restart dns , netlogon service on each dc , client.
abhijit waikar - mcsa 2003|mcsa 2003:messaging|mcts|mcitp:sa
Windows Server > Directory Services
Comments
Post a Comment