• Home
  • Topics
    • Office 365
    • Teams
    • SharePoint
    • Exchange 2019
    • Exchange 2016
    • Exchange 2013
    • Hybrid
    • Certificates
    • PowerShell
    • Migration
    • Security
    • Azure
  • Blog
  • Podcast
  • Webinars
  • Books
  • About
  • Subscribe
    • Facebook
    • Twitter
    • RSS
    • YouTube

Practical 365

You are here: Home / Exchange Server / Manually Configuring DNS Lookups for Exchange Server 2013

Manually Configuring DNS Lookups for Exchange Server 2013

April 2, 2013 by Paul Cunningham 44 Comments

In some Exchange Server 2013 environments it will be necessary to manually configure the DNS servers that Exchange uses for external name resolution.

This is most common in environments where the internal DNS servers that the general server and workstation population uses for DNS cannot resolve external names (a security requirement for some organizations).

Obviously Exchange Server 2013 is a little different than your average server or workstation. DNS is a requirement for Exchange to be able to route outgoing email if a smart host is not being used.

To configure DNS lookups for an Exchange 2013 server in the Exchange Admin Center navigate to Servers, highlight the server you wish to configure, and click the Edit button.

exchange-2013-external-dns-01

In the DNS Lookups section drop down the list to either choose an adapter that has the correct DNS servers configured on it, or if no adapter has DNS servers configured that can resolve external names choose Custom Settings.

exchange-2013-external-dns-02

If you have chosen custom settings you can add the IP addresses of DNS servers.

exchange-2013-external-dns-03

Click Save to commit the changes.

The same configuration options also exist for internal DNS lookups.

Be cautious when configuring Exchange Server 2013 DNS lookups in this manner, and make sure you test the changes afterwards to ensure mail flow is still functioning correctly. Misconfigured DNS settings can cause problems with Exchange 2013 such as sent items being stuck in the OWA Drafts folder.

Exchange Server DNS, Exchange 2013, Mail Flow, Transport

Comments

  1. Techi Jack says

    February 11, 2020 at 8:48 pm

    Really useful information share by “Paul Cunningham ” regarding Manually Configuring DNS Lookups for Exchange Server 2013,
    If you need any other information regarding Exchange Server Split-Brain DNS Configuration
    you can try TechiJack

    Reply
  2. Markus Greiner says

    January 22, 2020 at 4:47 pm

    Thank You
    Support adds value!
    I had lost some Adapter and because I went back and saved again, thank G*d it worked.
    Mark Germany

    Reply
  3. ToniIfeu says

    December 17, 2019 at 1:22 am

    Thx a lot Paul!

    Reply
  4. Mohammed says

    July 15, 2019 at 12:25 am

    Emails from outside are getting delayed ,

    If i use exrca inbound smtp , email comes in
    but When i send from any Gmail or outlook it delays for 30 minutes, how to troubleshoot.

    Reply
  5. uzi says

    September 12, 2018 at 8:21 pm

    Hi Paul,

    Appreciated your support !

    Dear i have a problem with sending Emails that trigger from Exchange Queue but could not reach the recipient . Receiving Email fine.

    Scenario:

    Having Two ISP

    1st ISP where our domain hosted and he gave me smart host IP as a relay agent.
    MX Record Update.

    2nd ISP from we using DIA line with public IP for our Exchange Server.
    PTR Record updated for rDNS.
    Put IP for External DNS lookup

    Kindly need your help to sort out the problem.

    Reply
  6. Steve says

    April 3, 2018 at 12:01 am

    Hi Paul,

    I upgraded from exchange 2010 to 2016 on prem. Everything is working fine but Outlook Anywhere is not, i need to connect to corporate vpn to sync my emails,… why is that ?

    I have a public SAN cert configured as well, Public DNS records set.

    please help.

    Reply
    • Paul Cunningham says

      April 3, 2018 at 11:43 am

      You can use the exrca.com tool to perform external testing to try and identify the cause of the problem.

      Reply
  7. Andrew Murrell says

    March 23, 2018 at 9:19 pm

    Hi
    I set up exchange 2016 to look at external dns Servers as our organization does not allow external resolution. However, it seems to have caused an issue with the exchange services not starting up properly.

    When doing nslookup on any other server or computer for mail.xxxxx.com they resolve to the internal it address of our exchange server. But doing this on the exchange server it resolves to the external IP address. When I disable the external lan and restart exchange all services apart from a couple start up fine.

    How can I resolve this issue

    Reply
    • Paul Cunningham says

      March 23, 2018 at 10:23 pm

      What is the “external lan” you’re referring to?

      Reply
  8. Naveen says

    March 30, 2017 at 1:10 pm

    Hello Friend i have a big problem i have configured Microsoft Exchange Server 2016 i am not able to send the email all emails are going in Draft Folder while sending from OWA
    Please help me

    Reply
  9. Tracy Kelley says

    March 12, 2017 at 10:33 am

    Can this be done to resolve internally? Our Exchange server DNS name is different that the Exchange name so we get a certificate error. I have resolved the issue by changing a local host file on a test PC, but was sure the best way to make the fix globally thru out our local domain.

    Reply
    • Paul Cunningham says

      March 13, 2017 at 9:13 am

      There’s a few things you’ll need to look at with regards to the client access namespace configuration, and the SSL certificate that’s installed, as well as your use of DNS. I think this will be the best place for you to start:

      https://practical365.com/exchange-server/avoiding-exchange-2013-server-names-ssl-certificates/

      Reply
  10. Barry McKeown says

    October 29, 2016 at 5:00 am

    MX A Cname

    Reply
  11. Barry McKeown says

    October 29, 2016 at 5:00 am

    And as Paul said , last 2 issues DNS DNS DNS

    Reply
  12. Barry McKeown says

    October 29, 2016 at 4:58 am

    top notch as allways

    Reply
  13. Chamu says

    October 20, 2016 at 1:36 am

    Great articles you have Paul. They are so valuable.

    Reply
  14. Prakash says

    June 12, 2016 at 1:02 pm

    Hi..
    I have indtalled exchange 2016 and my issue is

    From inside the office outlook works fine but from outside the office outlook doesnt connect to server.

    From outside the office outlook setup is not getting autodiacovery.

    Help what could be the reason..

    Reply
  15. Hozayfa says

    May 27, 2016 at 12:56 am

    hi
    what is the required DNS configuration for internal send and receive locally with Exchange 2013

    Reply
  16. Edward says

    January 6, 2016 at 7:40 pm

    Our website stopped resolving on our local network after installing mail exchange server 2013.
    What could be the cause?

    Reply
    • Paul Cunningham says

      January 6, 2016 at 9:18 pm

      Sounds like a DNS problem to me.

      Reply
  17. Ronie says

    July 8, 2015 at 7:12 pm

    Dear Paul,

    I was following your tutorials on Exchange 2013. Currently, I have one client who is consulting for exchange setup. They have two domain name (test.com and test.net) and they will be using only one exchange server.

    I am currently testing exchange configuration in my own Lab.

    The scenario is as follow,

    Local Domain name – test.local
    External Domain names – test.com & test.net

    Domain registrations are done as follow,

    Test.com
    A host – 203.6.6.6
    MX – mail.test.com

    Test.net
    A host – 203.6.6.6 (same public IP as in Test.com)
    MX – mail.test.net

    I have added test.com & test.com in accepted domain list. I have created one send connector.
    I also have done mail flow accordingly.

    I am having some issues those are .

    1. Whenever I sent emails from user1@test.com & user2@test.net to Gmail, those go into Gmail’s span folder. Can you please explain me how can I resolve this ?

    2. I have tested by sending to both user1@test.com & user2@teset.net from Gmail and found out.

    If user1 received that email, user2 didn’t receive it on time (received 10 -20 minutes later)
    If user 2 received that email, user1 didn’t receive it on time ( received 10 -20 minutes later)

    Please help me with this.

    Best Regards,
    Ronie

    Reply
  18. Tom says

    April 16, 2015 at 1:37 am

    My problem is related to DNS but is a little a bit different.
    I have smart host in Comcast to send emails from my company.
    I have setup Domain controller with DNS server and revers lookup. I’ve created secondery DNS server on my Exchange server.
    Every time when I want to use smart host FQDN my emails stuck in the queue. If I use IP adress for smart hose, emails are going out if FQDN then not.
    NSLOOKUP from DNS server and from EXCHANGE is showing Comcast smtp.hcm1.comcast.net with right IP return.
    I’ve setup DNS lookup on my Exchange using this article and is not working if I use comcast name instead of IP.

    Any suggestions ?

    Reply
    • Paul Cunningham says

      April 16, 2015 at 10:12 am

      You’ve installed the DNS Server role on your Exchange server?

      Aside from that… if mails are stuck in your queue, you need to look at the reason why. Use Get-Queue | Get-Message to see more details. Do Google/Bing searches on the error/message that you see as the reason for the email being stuck. There’s lots of possibilities.

      Reply
    • Anil says

      September 5, 2016 at 12:34 pm

      I have the same issue as Tom. Did you find a solution.

      Reply
  19. Akshita says

    April 10, 2015 at 6:14 pm

    Hi

    I have configured Exchange Server 2013 sp1 in my test environment. I am able to send and receive emails within my domain. Also, I am able to send emails to other domains(by following your blog https://practical365.com/configuring-outbound-mail-flow-in-exchange-server-2013/). How do I make sure that I am able to receive emails from other domains as well?

    I am testing the Conditional Access Exchange on-premises policy in Micrsoft Intune.

    Reply
    • Paul Cunningham says

      April 12, 2015 at 7:00 pm

      Send some test emails from another domain (gmail, outlook.com, yahoo.com…)

      Or use the exrca.com inbound SMTP test.

      Reply
  20. Blaudfaust says

    January 19, 2015 at 8:10 pm

    I have configure my exchange 2013 server, when email are send, it goes out with the mail1.local instead of the HELLO or EHLO response name which is mail1.sl

    how can I enable the mail sever sending email with the .sl instead of .local

    Reply
    • Paul Cunningham says

      January 20, 2015 at 8:55 am

      You can configure the FQDN on the Send Connector properties.

      Reply
  21. Nagesh says

    November 26, 2014 at 5:58 pm

    Hi Paul,

    I have a lab environment. Where i installed Exchange 2013. I want to send/receive emails from internet. How to configure connectors to achieve this. The domain is not registered in. Just i am using for lab purpose for testing only.

    Reply
    • Paul Cunningham says

      November 27, 2014 at 10:39 am

      Without a registered domain name you won’t be able to receive emails.

      Inbound mail flow (MX records):
      https://practical365.com/mx-record/

      Outbound mail flow:
      https://practical365.com/configuring-outbound-mail-flow-in-exchange-server-2013/

      Accepted Domains:
      http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx

      Reply
  22. Joshua Meade says

    October 27, 2014 at 5:51 pm

    Hello I am having issues with inbound emails. My dns for my domain name is hosted using Rackspace.com free dns service so i am not sure how to get my server to look for the right dns when its not hosted on the mail server its self

    Reply
    • Paul Cunningham says

      October 27, 2014 at 9:16 pm

      For inbound mail flow you need to look at your MX record(s).

      Read these:
      https://practical365.com/mx-record/
      https://practical365.com/exchange-2013-mail-flow/

      Reply
  23. Sajeev says

    October 19, 2014 at 11:31 am

    I have “techgreen.local” as a local domain. If i want to create techgreen.sg domain for email. If i use split brain DNS. Do i have to create name sever in both zone? if yes how? Please help

    Reply
    • Paul Cunningham says

      October 19, 2014 at 8:47 pm

      The name servers are the servers hosting the DNS zone. Yes both zones will have name server records in them.

      Reply
      • Sajeev says

        October 19, 2014 at 11:27 pm

        Thanks bro

        Reply
  24. sajid says

    August 28, 2014 at 7:36 pm

    hi paul,

    How to fixing spf issue

    Reply
  25. Peter says

    August 20, 2014 at 10:06 pm

    Hello Paul,

    What is the exchange power shell command to Configuring DNS Lookups for Exchange Server 2013?? Thanks,

    Reply
    • Paul Cunningham says

      August 20, 2014 at 11:09 pm

      Set-TransportService has a parameter for that.

      http://technet.microsoft.com/en-us/library/jj215682(v=exchg.150).aspx

      Reply
  26. Jyothi Pradeep Kollipara says

    August 1, 2014 at 6:28 pm

    Thanks a lot for this article. This solves the missing piece in my puzzle. All blogs on the internet were only talking about the setup of mail flows. The information on setting up DNS lookups was very useful.

    Reply
  27. Hendra says

    April 27, 2014 at 3:07 am

    Thank you very much,, The Windows Exchange Transport Services is running…

    Reply
  28. Manoj says

    September 23, 2013 at 9:52 pm

    Hi,

    I am unable to change External DNS server in DNS lookup as I am getting some error
    “This service cannot be started, either because it is disabled or because it has no enabled device associated with it. (Exception from HRESULT:0x80070422)

    Please help me out how to fix it.
    if possible please let me know how to do this via Exchange Management Shell?

    Thanks in Advance..

    Reply
    • Tony says

      September 29, 2013 at 12:54 pm

      Hi Manoj,

      All Exchange services are turned on ?

      Thanks,
      Tony

      Reply

Leave a Reply Cancel reply

You have to agree to the comment policy.

Recent Articles

  • The Practical 365 Weekly Update: S2, Ep 8 – What to expect in 2021, Solarigate, TLS in Exchange and new Teams updates
  • Security updates released for Exchange and SharePoint Servers 2010 to 2019
  • The Practical 365 Weekly Update: S2, Ep 7 – Urgent Exchange security updates, new Teams features launch
  • How to train your users against threats with Attack Simulation Training
  • Fall 2020 roundup of compliance updates
Practical 365

Related Posts

Related Posts

Training Courses

  • Configuring and Managing Office 365 Security
  • Office 365 Admin Playbook
  • Exchange 2016 Exam 70-345
  • Managing Exchange Mailboxes and Distribution Groups in PowerShell
  • More Training Courses...

Recommended Resources

  • Office 365 Security Resources
  • Office 365 Books
  • Exchange Server Books
  • Exchange Server Migrations
  • Exchange Analyzer
  • Digicert SSL Certificates

About This Site

Practical 365 is a leading site for Office 365 and Exchange Server news, tips and tutorials. Read more...

Find out more about advertising with us.

Contact us


Subscribe to our newsletter
  • Facebook
  • Twitter
  • RSS
  • YouTube

Copyright © 2021 Quadrotech Solutions AG · Disclosure · Privacy Policy
Alpenstrasse 15, 6304 Zug, Switzerland