I have a single 2012 R2 domain controller and single Exchange 2013 SP1 installation.
It looks like the internet has run out of suggestions. I've used NSlookup with set q=mx to make sure the internal DNS server points to the only Exchange server. I made reverse lookup zones and make a PTR record for the mail server and domain
Like badguy643, my results to test-servicehealth comes out all True.
The results of get-transportservice | Format-list shows internalDNSservers and externalDNSservers to be correct. Oddly enough, it says that internalDNSAdapterEnabled to be false. But when I use set-TransportService to change the attribute, it
says that it was successful but no setting was changed. Perhaps the get-transportservice has a false negative?
I've rebooted a few times and restarted the Transport Submisison Service after waiting 10 minutes after bootup with no better results.
What do I need to do to make my single Exchange server recognize it's own hand? All my tests are with internal email from one mailbox to another. I'm getting desperate enough to pay the $270 to have Microsoft fix it .
Edit - it seems as though I'm getting an non-existent domain error on the connectivity log. Since my logon domain is different from my email domain, it's causing this problem as it's trying to send internal email using my logon domain. I'll have
to remove the public DNS server since it doesn't want to prioritize the internal one.
Sunday, August 03, 2014 11:52 PM