Applies to: Exchange Server 2013
Topic Last Modified: 2012-06-05
The content in this topic hasn't been updated for Microsoft Exchange Server 2013. While it hasn't been updated yet, it may still be applicable to Exchange 2013. If you still need help, check out the community resources below.
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection
Microsoft® Exchange Server 2007 setup cannot continue because communication with the primary Domain Name System (DNS) server cannot be established.
Exchange 2007 setup requires that the local computer communicate with the authoritative DNS database for the domain.
Microsoft Exchange depends on DNS to resolve the IP Address of its next internal or external destination server.
Communication with the primary DNS server can fail for the following reasons:
- The local TCP/IP configuration does not point to the correct
DNS server.
- The DNS server is down or unreachable because of a network
failure or other reasons.
To resolve this issue:
- Verify that the local TCP/IP configuration points to the
correct DNS server.
-
Review the local TCP/IP configuration:
For more information, see "Configure TCP/IP to use DNS" (http://go.microsoft.com/fwlink/?LinkId=68094).
- Verify that the DNS server is running and can be contacted.
-
Verify that the DNS server is running by doing one or more of the following checks:
- Look at the DNS server status from the DNS Administration
program on the DNS server.
- Restart the DNS server.
For more information, see "Start, stop, pause, or restart a DNS server" (http://go.microsoft.com/fwlink/?LinkId=62999).
- Verify the DNS server responsiveness by using the
nslookup command.
For more information, see the instructions in "Verify DNS server responsiveness using the nslookup command" (http://go.microsoft.com/fwlink/?LinkId=63000).
- Look at the DNS server status from the DNS Administration
program on the DNS server.