What to Put for Server in Microsoft Exchange: Correct DNS Records Explained

This FQDN acts like your Exchange server's digital address—it tells Outlook exactly where to find your email, calendar, and contacts. 🔥 If you're setting up Outlook manually, this field is critical, but most users rely on the Autodiscover service to auto-fill it.

I've seen countless connection issues fixed simply by verifying this one setting, especially when users mix up internal (LAN) vs. external (Internet) URLs. For hybrid Exchange environments, you might need separate entries for internal and external access, which is why consulting your admin is non-negotiable.

Understanding Microsoft Exchange server DNS requirements

DNS records act as the invisible bridge between your email client and Exchange server, translating human-readable names into machine-understandable IP addresses. The Autodiscover record (type SRV) is particularly critical—it automatically configures Outlook by pointing to your Exchange server's FQDN (like mail.yourdomain.com).

Without this, Outlook won't know where to find your mailbox, calendar, or contacts, leading to sync failures. 🔥 The MX record (Mail Exchange) handles incoming emails, while the SRV record directs client connections to the correct protocol (HTTP/HTTPS) for Outlook's autoconfiguration.

Here's where things get technical: Exchange uses two distinct URLs—internal (for LAN connections) and external (for remote access). A common mistake is using the wrong URL type. For example, entering your internal URL (like exchange.internal) when connecting remotely forces Outlook to fail with "cannot connect to server" errors.

The FQDN must match your public DNS configuration exactly—typos or mismatches (e.g., missing "mail." prefix) break connections entirely. Think of it like mailing a letter: if the address is wrong, it never arrives.

Misconfigurations often appear as cryptic errors like "The connection to Microsoft Exchange is unavailable" or "Outlook cannot connect to your mailbox." These typically stem from one of three issues: missing SRV records, incorrect FQDN entries, or firewall blocking port 443.

The Autodiscover service relies on these records to dynamically populate Outlook settings, so even a single missing record can cascade into connection failures. For hybrid Exchange setups, you might need to configure both internal and external URLs separately in your DNS, adding another layer of complexity.

Let's compare correct vs. incorrect configurations. A proper Autodiscover SRV record looks like this: autodiscover.tcp.yourdomain.com pointing to mail.yourdomain.com. An incorrect version might omit the underscore prefix or use an IP address instead of a domain.

Similarly, the Server field in Outlook should always use the FQDN (e.g., mail.yourdomain.com), never an IP address or partial domain like yourdomain.com. This precision ensures Outlook can resolve the server's location reliably across all devices and networks.

What most users don't realize is that DNS propagation can take up to 48 hours after changes. During this window, even correct configurations may fail temporarily. To test your setup, use PowerShell's Test-OutlookConnectivity cmdlet—it simulates Outlook's connection process and pinpoints exactly where failures occur.

For example, if the test fails at the "Autodiscover" stage, you know to check your SRV records first. This tool is your best friend for diagnosing silent DNS issues that might be invisible to casual troubleshooting.

Pro tip: If you're managing a hybrid Exchange environment (combining on-premises and cloud), you'll need to configure both internal and external URLs in your DNS. The internal URL might be exchange.internal.yourdomain.com, while the external URL uses your public domain.

This dual configuration ensures seamless access whether users connect from the office or remotely. Always verify these settings against your Exchange admin center's configuration to catch discrepancies before they cause outages.

Remember: DNS isn't just about typing a name—it's about creating a precise, trustworthy path between your client and server. A single misplaced character or missing record can turn a smooth email experience into a frustrating puzzle.

That's why the FQDN isn't just a field—it's the foundation of your entire Exchange communication system. 💫

Step-by-step guide to configuring Exchange server settings

Start by opening your Outlook desktop app and navigating to File > Account Settings > Account Settings. Select your Exchange account and click Change.

In the server settings window, you'll see a field labeled Server—this is where you enter your Exchange server's fully qualified domain name (FQDN), like mail.yourdomain.com.

If you're unsure what to use, check with your IT admin or look in your Exchange admin center under servers > virtual directories for the correct external URL. 🔥

For mobile devices, the process varies slightly. On iOS, go to Settings > Mail > Accounts > Add Account > Exchange and enter your email address. Outlook for iOS will auto-fill the server field if Autodiscover is working, but you can manually verify it matches your FQDN.

On Android, use the Microsoft Outlook app and tap Settings > Add Account, then enter your credentials—it should auto-detect the correct server. If it doesn't, manually enter the FQDN in the advanced settings.

Once you've entered the server name, test your connection using PowerShell. Open a PowerShell window as admin and run Test-OutlookConnectivity -Identity your@email.com -MailboxExchange. This command simulates Outlook's connection process and highlights where issues occur. Common errors like "Cannot connect to server" often point to DNS misconfigurations or firewall blocks.

If the test fails at the Autodiscover stage, double-check your SRV records in DNS. For remote users, ensure you're using the external URL, not the internal one.

Here’s a quick checklist to avoid mistakes:

• Internal vs. External: Use internal URLs (e.g., exchange.internal) only for office networks; external URLs (e.g., mail.yourdomain.com) are for remote access.
• FQDN Format: Always include the mail. prefix (e.g., mail.yourdomain.com, not just yourdomain.com).
• HTTPS Required: Ensure your server supports HTTPS—Outlook won’t connect without it.
• Firewall Rules: Verify ports 443 (HTTPS) and 80 (HTTP) are open for Autodiscover.

If you're still stuck, try clearing Outlook's cached credentials. Go to Control Panel > Mail > Show Profiles > Properties > Security and click Remove under Cached Exchange Mode. Restart Outlook and reconnect—this often resolves authentication issues tied to stale server entries. For hybrid Exchange environments, you might need to configure both internal and external URLs separately in your Outlook profile, which is why consulting your admin is critical. ✨

Pro tip: Bookmark your Exchange admin center’s server configuration page for quick reference. It’s the fastest way to confirm your FQDN and troubleshoot connection issues without digging through DNS records every time.

Most admins also provide a test email address for verifying settings—send yourself a test message to confirm everything’s working before rolling out changes to your team.