Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Exchange 2013 and Internal DNS Sending Mail Issue

Posted on 2014-01-27
3
Medium Priority
?
566 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
  • 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

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
In this post, we will learn to set up the Group Naming policy and will see how it is going to impact the Display Name and the Email addresses of the Group.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

572 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