Reply
Accepted Solution

Exchange Issue after Infoblox Migration

[ Edited ]
maleek20
Techie
Posts: 11
3862     0

Dear All

 

After migrate DNS "Integrated with AD" and intall bind tool in AD servers everything is working fine for 7 hours

then suddenly email stop working . we add DNS ip address of Infoblox to alll Exchange servers and restart them 

and we faced same issue but suddenlt send emails then again stop.

 

Can anyone help us and advise why Exchange keep hanging 

 

Note all services in networking fine except Exchange server 2013

 

Error below  nd the below IP is related to Microsoft DNS

nhic-mbx01

 

EventID: 0x00000847 (2119) - Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3156). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain NHIC.LOCAL  The query was for the SRV record for _ldap._tcp.dc._msdcs.NHIC.LOCAL  Common causes of this error include the following:  - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses: 172.21.0.25 172.21.0.26 172.20.0.226 172.20.0.225 fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe   - One or more of the following zones do not include delegation to its child zone: NHIC.LOCAL LOCAL . (the root zone)               19:38:32 11/07/15           

 

nhic-mbx02

 

EventID: 0x00000847 (2119) - Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3724). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain NHIC.LOCAL  The query was for the SRV record for _ldap._tcp.dc._msdcs.NHIC.LOCAL  Common causes of this error include the following:  - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses: 172.21.0.26 172.21.0.25 172.20.0.225 172.20.0.226 fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe   - One or more of the following zones do not include delegation to its child zone: NHIC.LOCAL LOCAL . (the root zone)

Re: Exchange Issue after Infoblox Migration

Adviser
Posts: 85
3863     0

Are all these servers Infoblox? 172.21.0.25 172.21.0.26 172.20.0.226 172.20.0.225 

 

Also, when you check the auth zone for which the AD DNS servers are trying to update, do you see the underscore zones created?

 

Have you tried a manual ipconfig /registerdns from a DC?

 

There could be many possibilities for errors, I suggest you troubleshoot to narrow down the issue first before possibly opening a support ticket. Read the admin guide as well, it is helpful for helping you with AD integration.

Re: Exchange Issue after Infoblox Migration

Adviser
Posts: 147
3863     0

From the error messages it would appear that their are missing Active Directory associated SRV records from the DNS zone. These records should be dynamically generated by your Domain Controllers and updated into the authoritative DNS domain on the Infoblox DNS.

 

Ensure the appropriate domains are configured within Infoblox to support Active Directory updates. Also ensure the Domain Controllers are configured to point to the Infoblox DNS for their DNS resolvers. Typically a restart of the netlogon service on the DC will cause it to check and register any appropriate records into DNS.

 

If there are SRV records that were staticallly created as part of a migration process you may need to clear those out and then allow AD to dynamically recreate those records.

 

If you are not able to find the issue I would suggest contacting Support for assistance with identifying the root cause of the configuration issue.

 

Hope that helps!

Check out our new Tech docs website at http://docs.infobox.com for latest documentation on Infoblox products
Showing results for 
Search instead for 
Do you mean 

Recommended for You