Exchange 2010 DNSConnectorDelivery Retry
We have an Exchange 2010 server that all of a sudden started going into a Retry status on DNSConnectorDelivery. I can stop and restart the Transport service and it will send mail out for a few minutes and then stop again. Inbound email works fine as does internal email. only outbound appears to be affected.
tshearon
Do you send mail to the internet using MX records or through a smart host?
ASKER
sending through MX.
Also another bit of info I just discovered. I did an Nslookup on the server and it does not resolve google.com. it is using IPv6. so I disabled the IPv6 and ran the nslookup and it was successful.
I restarted the Transport service and it would not start with IPV6 disabled?
Also another bit of info I just discovered. I did an Nslookup on the server and it does not resolve google.com. it is using IPv6. so I disabled the IPv6 and ran the nslookup and it was successful.
I restarted the Transport service and it would not start with IPV6 disabled?
Don't disable it. You need it for the service to start. Just simply unselect it on the properties of the network adapter you are using.
ASKER
Sorry- that is what I meant. I unchecked it on the adapter properties. but transport service will not start with it unchecked.
hrmm. You can disable it in the registry and it should still start. Try this:
http://busbar.blogspot.com
http://busbar.blogspot.com
ASKER
I did this...
Open Registry Editor.
Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
In the details pane, click New, and then click DWORD (32-bit) Value.
Type DisabledComponents, and then press ENTER.
Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.
Transport Starts, but nslookup is still using IPv6 and not resolving.
Open Registry Editor.
Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
In the details pane, click New, and then click DWORD (32-bit) Value.
Type DisabledComponents, and then press ENTER.
Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.
Transport Starts, but nslookup is still using IPv6 and not resolving.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did not restart server or uncheck it... I will try both and report back
ASKER
removed the check mark from IPV6 and rebooted. mail is currently sending after the reboot. After the reboot I stopped and started transport and it was successful. nslookup resolves correctly now.
I will give it 30 minutes and test email sending to see if it still works.
I will give it 30 minutes and test email sending to see if it still works.
Glad to hear. Let me know how it goes.
ASKER
still not working.
ASKER
I checked dns and flushed the cache and the send connectors. all looked. ipconfig flushdns and registerdns.
that started sending mail. i did not stop and start transport service. hoping this fixed it
that started sending mail. i did not stop and start transport service. hoping this fixed it
Flushing and registering DNS should have no effect since after restarting there were no changes made that would affect DNS config or cache.
ASKER
It's still working. I can only assume the DNS flush or register did it. Thank you for the assistance.