Exchange Server down time because of PUBLIC DNS ???
AD-tpology-converted-merged.pdfDear Experts,
Hope u are doing well, I need your suggestions, I am facing the issue of Exchange server losses the internet connection(Image is in attachment) and down time observed. Mr. Mahesh helped me and We found lookback IP was added as an alternative DNS in exchange server. So I removed it. And I assume the problem is solved. But again I have observed exchange server down time same as before...Therefore I did troubleshoot and I found the same alternative DNS lookback ip as in Exchange server, 127.0.0.1 was added as an alternative DNS in my Domain controller, I dont understand what is the actually problem? Is the AD server alternative DNS and Exchange server alternative DNS was creating this problem together.
Can you please advice me on this issue?
Now I have removed lookback IP from both exchange and DC, So can I assume it will not looses its conenctivity with DC?
Please review the AD and Exchange pics.
MAny Thanks
Hope u are doing well, I need your suggestions, I am facing the issue of Exchange server losses the internet connection(Image is in attachment) and down time observed. Mr. Mahesh helped me and We found lookback IP was added as an alternative DNS in exchange server. So I removed it. And I assume the problem is solved. But again I have observed exchange server down time same as before...Therefore I did troubleshoot and I found the same alternative DNS lookback ip as in Exchange server, 127.0.0.1 was added as an alternative DNS in my Domain controller, I dont understand what is the actually problem? Is the AD server alternative DNS and Exchange server alternative DNS was creating this problem together.
Can you please advice me on this issue?
Now I have removed lookback IP from both exchange and DC, So can I assume it will not looses its conenctivity with DC?
Please review the AD and Exchange pics.
MAny Thanks
I am not aware that exchange also set with loopback address
Just remove loopback from exchange and keep only dc ip as preferred dns
Loopback refer to localhost, since exchange is not an dns server, u must remove loopback
On DC we already set loopback as secondary dns
Just remove loopback from exchange and keep only dc ip as preferred dns
Loopback refer to localhost, since exchange is not an dns server, u must remove loopback
On DC we already set loopback as secondary dns
Your DCs should have it's own IP as the primary DNS server, and the IP of another DC (if you have one) as it's secondary DNS server.
Your Exchange servers should only have primary and secondary DNS server settings pointing to DCs, and never a loop back. Again there should be no loop back on your exchange servers for DNS, it should point to a DC.
Your Exchange servers should only have primary and secondary DNS server settings pointing to DCs, and never a loop back. Again there should be no loop back on your exchange servers for DNS, it should point to a DC.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
AD requires one (or more) DNS that provide the domain name translation.
This DNS must be the ONLY DNS referenced from all domain members. (Work stations, servers, etc.).
So it makes perfect sense to have localhost (127.0.0.1) on a DC. A DC should be able to inquire itself. (It it is running then DNS server is also running).
Any Backup DC also make sense to have 127.0.0.1 for themselves as they synchronize DNS with the current master.
Any other AD domain member (servers, workstations) ONLY HAVE the DC ('s) as DNS server.
Any non DC Server, any Workstation DOES NOT have any other DNS server for lookup.
If internet name resolution is needed, use forwarding from the DNS server(s) themselves.
Failure to do so will cause connections issues within the domain. As all kind of systems are unable to find parts of the AD domain.