?
Solved

Exchange 2013 and Internal DNS Sending Mail Issue

Posted on 2014-01-27
3
Medium Priority
?
553 Views
Last Modified: 2014-01-27
Here is my scenario.
Exchange 2013 sitting on a 2012 Server in a domain.
Has regular LAN IP address, and is single email server for a company.
Uses Internal DNS of PDC in domain.
Having an issue with only 1 client when sending email.
So on the exchange box, i did an nslookup and got their email server name, which from the same exchange box, i can ping.  so I also did a tracert and a telnet to that email server on port 25 and it all works.
But when I check the queue viewer app, it tells me unable to connect, unable to resolve DNS name.  So i scratched my head, and changed the DNS IP to the ISP dns rather than internal and it works.  Only problem is all internal clients on outlook stop working, so i changed it back.
So i try another internal DNS server and no luck either.  I dont understand how this is possible.  If i can resolve in a command prompt and via telnet, why doesnt the exchange send connector resolve it?  
Ill take any suggestion...
0
Comment
Question by:PlatinumInfo
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 5

Accepted Solution

by:
Jullez earned 2000 total points
ID: 39813392
Please try the following:
Test-SmtpConnectivity -Identity <Name of your 2013 MailboxServer>

And take a look at this new blog post by Tony Redmond -
http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages/
0
 

Author Comment

by:PlatinumInfo
ID: 39813475
Didnt know you could set those settings in exchange, thought it was driven by the NIC.
Learn something new every day.  Thanks Jullez!
0
 
LVL 5

Expert Comment

by:Jullez
ID: 39813483
You are welcome! Exchange 2013 is a different animal...I learn something about it everyday as well.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question