-
Well, it seems that you can resolve internet names when you have your external set up as forwarder on your internal dns server. Once you take that out, you can resolve nothing at all. This tells me that although the ISP's dns servers are setup up for forwarding on your internal dns server, queries to your internal dns server are not being forwarding to the ISP's dns server. Know what I mean?
Now, the requests are being sent to your external dns server. It appears that this dns server is not able to resolve the mx records.
Two options for you. Ensure that, from your internal dns server, you can query the ISP's dns servers. I believe this will sovle the issue. ( To test this, remove your external dns server from the forwarding list. Make appropriate adjustments until you are able to resolve internet names using only the ISP's dns servers as your forwarders.)
Also ensure that you can resolve the mx records from your external dns server. From what you've told me, it appears the breakdown lies with this server. You can even try to set forwarders to the ISP's dns servers on this. It may help.
-
I removed my external dns server from the forwarders list. Now heres the curveball. I setup an email account using a different domain name. And this time the mx record got resolved. What the hell is going on now????? Why did find a different mx record but couldn't find this mx record.
-
Is this domain name in question the same as the AD domain name? If so, the internal dns server would think that it is authoritative for that zone, and if there are no mx records in there then it might not forward requests on to other servers.
Know what I mean?
Thats a long shot, but its possible.
-
Thats it man. That was the problem. I had the Ad and the domain name as the same. Whew thats a boat load off. Thank you so much man you really made my day.
Thanx
-SOIA
-
Hey I'm glad we got it fixed! I was starting to take this problem personal! :)
Take Care! :D
