Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsIf an MX record points to the wrong mail server, change it in the DNS zone that is authoritative for your domain and enter the exact MX records published by your email provider. Then verify the public DNS answer. If it matches but messages still do not arrive, investigate the mail service rather than repeatedly editing a correct record.
1. Confirm which mail service should receive your domain’s email
MX records tell other mail systems which servers handle incoming email for a domain. The correct destination is determined by the email service you actually use—not by a universal MX value. Find that provider’s current setup instructions and note every required MX destination and priority.
As an Amazon Associate I earn from qualifying purchases.
For example, Google Workspace’s current single-record setup specifies smtp.google.com at priority 1. Google Workspace’s instructions also say to remove other MX records during that setup. This is Google-specific guidance, not a value to use for domains hosted elsewhere. Use the complete record set required by your own mail provider.
Recommended Free Tools
Google says domains that began using Workspace before 2023 may have legacy aspmx records. If mail is working, Google says those domains do not need to change them and that the legacy values remain supported. See Google Workspace’s MX setup instructions for its current configuration and qualifications.
#1 Best Overall
2. Find the authoritative DNS zone
Edit DNS wherever the nameservers for your domain are managed. This may be your registrar, but it could instead be a separate DNS provider. Signing in to the registrar is not enough if another company’s nameservers serve the domain.
In the DNS provider’s control panel, look for a section labeled DNS records, DNS management, or a similar domain-management option. You do not need to switch providers to fix an MX record; you need access to the provider serving the domain’s DNS zone.
3. Correct the MX records for the right name
Review all MX rows for the domain name that should receive mail. Remove, retain, or add records according to the mail provider’s instructions. Multiple MX records can be valid: their numeric priorities establish preference and fallback order. Google’s DNS basics guide explains that if delivery through the highest-priority record fails, the next-priority record can be used.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Check the host or name field. For mail to the domain root, the DNS interface may expect a blank value or
@. The correct entry depends on that provider’s interface. Do not putwwwor another subdomain there unless that is specifically where you intend to change mail routing. - Enter the destination exactly as instructed. Some DNS interfaces require a trailing dot after the destination; others add it automatically or provide a preset. Follow the interface’s guidance rather than adding or removing the dot by guesswork.
- Set the required priority. Match the provider’s published value for each record. Do not assume that every provider uses the same number or requires only one MX record.
- Review the complete set before saving. Check for an old or unintended destination, a duplicate, or a missing provider-required row. The intended provider’s instructions determine which records belong.
4. Verify the public MX answer
A successful save in the control panel does not prove that the public DNS answer changed. Query the domain’s MX records with a DNS lookup tool and compare every returned destination and priority with the configuration required by your email host. Google Workspace administrators can use Google Admin Toolbox Dig, linked from Google’s setup guidance.
If the lookup still shows the old destination, check whether you edited the zone served by the domain’s nameservers, whether the host/name field created a record for the wrong name, and whether an old or duplicate MX row remains. A resolver may also still have a cached answer.
5. Allow caches to update
Mail senders do not necessarily see a DNS change as soon as it is saved. Cached answers can remain in use according to DNS time-to-live behavior and resolver state. Google Workspace says recognition of its new MX records can take up to 72 hours; that is Google’s stated possible timeframe for Workspace setup, not a guaranteed update period for every provider or resolver. Avoid treating the number as a universal propagation deadline.
Rank #4
6. If the MX record is right but mail is still missing
Once a public lookup shows the record set required by your email provider, move on to the mail service itself instead of making repeated DNS changes. The provider’s account, domain, or service setup may still need attention. For Google Workspace, confirm domain ownership and that Gmail is activated in the Admin console, then follow Google’s troubleshooting steps for receiving email in Gmail.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
