TacoFlavoredKisses
asked on
Added new DNS/AD server, DNS not replicating
We recently added a new server and did the following:
Made it a member server
Installed DNS
Ran DCPromo and added to existing domain
So far no zones have propagated into the new DNS server. Is there anything we can do to force the replication, or is there a step we are missing?
Made it a member server
Installed DNS
Ran DCPromo and added to existing domain
So far no zones have propagated into the new DNS server. Is there anything we can do to force the replication, or is there a step we are missing?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Then all the diagnostics if you could, it sounds like it's failing to replicate, it's something DCDiag should flag.
It's worth running it on the existing DC as well. How many DCs do you have at the moment?
Chris
ASKER
There are currently 5 domain controllers, not including the new one. DCDiag and NetyDiag look alright, here are the results:
H:\>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Inoc\INOADV03
Starting test: Connectivity
......................... INOADV03 passed test Connectivity
Doing primary tests
Testing server: Inoc\INOADV03
Starting test: Replications
......................... INOADV03 passed test Replications
Starting test: NCSecDesc
......................... INOADV03 passed test NCSecDesc
Starting test: NetLogons
......................... INOADV03 passed test NetLogons
Starting test: Advertising
......................... INOADV03 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... INOADV03 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... INOADV03 passed test RidManager
Starting test: MachineAccount
......................... INOADV03 passed test MachineAccount
Starting test: Services
......................... INOADV03 passed test Services
Starting test: ObjectsReplicated
......................... INOADV03 passed test ObjectsReplicated
Starting test: frssysvol
......................... INOADV03 passed test frssysvol
Starting test: frsevent
......................... INOADV03 passed test frsevent
Starting test: kccevent
......................... INOADV03 passed test kccevent
Starting test: systemlog
......................... INOADV03 passed test systemlog
Starting test: VerifyReferences
......................... INOADV03 passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : domain
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Running enterprise tests on : domain.local
Starting test: Intersite
......................... domain.local passed test Intersite
Starting test: FsmoCheck
......................... domain.local passed test FsmoCheck
--------------------------------------------------------------
H:\>netdiag
.....................................
Computer Name: INOADV03
DNS Host Name: inoadv03.domain.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 8, GenuineIntel
List of installed hotfixes :
KB923561
KB924667-v2
KB925398_WMP64
KB925902-v2
KB926122
KB927891
KB929123
KB930178
KB932168
KB933729
KB933854
KB935839
KB936357
KB936782
KB938127
KB938127-IE7
KB938464-v2
KB941569
KB943055
KB943460
KB943485
KB944338-v2
KB944653
KB945553
KB946026
KB948496
KB950760
KB950762
KB950974
KB951066
KB951698
KB951748
KB952004
KB952069
KB952954
KB953298
KB953838-IE7
KB954155
KB954600
KB955069
KB955759
KB955839
KB956390-IE7
KB956572
KB956802
KB956803
KB956841
KB956844
KB957097
KB958215
KB958469
KB958644
KB958687
KB958690
KB958869
KB959426
KB960225
KB960714
KB960715
KB960803
KB960859
KB961260-IE7
KB961373
KB961501
KB963027-IE7
KB967715
KB967723
KB968389
KB968816
KB969059
KB969947
KB970238
KB970430
KB971032
KB971180-IE8
KB971468
KB971486
KB971657
KB971737
KB971961-IE8
KB972270
KB973354
KB973507
KB973540
KB973687
KB973815
KB973869
KB973904
KB974112
KB974318
KB974392
KB974571
KB975025
KB975467
KB975560
KB975713
KB976662-IE8
KB977165-v2
KB977914
KB978037
KB978207-IE8
KB978251
KB978262
KB978706
KB979306
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : inoadv03
IP Address . . . . . . . . : 192.168.17.20
Subnet Mask. . . . . . . . : 255.255.240.0
Default Gateway. . . . . . : 192.168.17.1
Dns Servers. . . . . . . . : 192.168.5.22
192.168.17.20
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{91A58251-2D58-4AA1-9392-0B82034E0A85}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.5.22
' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server '192.168.17.2
0' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{91A58251-2D58-4AA1-9392-0B82034E0A85}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{91A58251-2D58-4AA1-9392-0B82034E0A85}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Passed
Secure channel for domain 'domain' is to '\\albad02.domain.local'.
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
ASKER
After running both of those, it appears DNS has now replicated. So I guess we just did not wait long enough
Your issue has been resolved but you can use below method to force dns replication.
To force the dns replication, you can goto dns admin console & right click the server & select update server data files.
This can be instantly forced the dns changes to other dns server.
To force the dns replication, you can goto dns admin console & right click the server & select update server data files.
This can be instantly forced the dns changes to other dns server.
That forcefully writes changes back to AD (DNS zones are loaded into memory), it doesn't force replication of those changes between DCs.
Chris
ASKER