How do you add email DNS records in Network Solutions?

Network Solutions is one of the oldest registrars, so many long-lived business domains still keep their DNS there. Its editor works like most others, with one naming difference: instead of a Host field, you choose Refers to and pick @, www or Other Host. Many domains there also already have an SPF record, which you must edit rather than duplicate.

This guide covers MX, SPF, DKIM and DMARC records in Network Solutions, using its help center and Microsoft's Network Solutions instructions. For background on the records, read SPF vs DKIM vs DMARC.

Is your DNS actually hosted at Network Solutions?

You can only edit records at Network Solutions if the domain uses its nameservers. Its DNS help article explains that managing records there requires moving to its nameservers, and warns: "When you move nameservers to Network Solutions, your existing nameservers will no longer be used." Its notice adds that websites and email hosted at other providers can be lost when you do that.

So check before you change anything. Look up the live nameservers with our MX Lookup. If they belong to another provider, such as Cloudflare, add your records there; our Cloudflare guide covers that case.

Where do you add DNS records in Network Solutions?

At the time of writing (October 2026), Network Solutions' current view works like this (Network Solutions Help):

1. Sign in and select Domains on the left side of the page.
2. Select the domain and click Manage.
3. Go to the DNS tab.
4. Click +Add Record. A pop-up window appears.
5. Choose the record type and fill in the fields.
6. Click Add.

To change an existing record, click the vertical ellipsis next to it, select Edit, make your change and click Edit to save. To change several at once, Network Solutions offers a Bulk Edit button, which "supports Advanced DNS records only."

Older accounts and Microsoft's Network Solutions instructions use a different path: Advanced Tools, then Manage next to Advanced DNS Records, then +ADD RECORD. Both reach the same records. A Classic View also exists, but it can't add or edit CAA records.

The fields:

Microsoft's instructions add two details. When you save a record with Refers to set to @, "The system will change this value to @ (None)." And for MX and CNAME targets, the value "CANNOT end with a period (.)", so remove any trailing dot your provider shows.

How do you add or edit an SPF record in Network Solutions?

SPF is a TXT record that refers to @. Network Solutions is direct about the rule: "Only one SPF record is allowed per domain," and "Publishing multiple SPF records can cause SPF authentication to fail, potentially affecting email deliverability." RFC 7208, section 3.2 says the same.

Many Network Solutions domains already have one. Its help article tells customers using its website contact forms to set their SPF record to this example:

v=spf1 include:spf.registeredsite.com include:spf.cloudus.oxcs.net ~all

1. On the DNS tab, find the TXT record that refers to @ and starts with v=spf1.
2. If it exists, open the vertical ellipsis, select Edit, add your provider's include before ~all or -all, and remove includes for services you no longer use.
3. If none exists, click +Add Record, choose TXT, set Refers to to @, paste the record into TXT Value and click Add.

For example, a domain moving to Microsoft 365 that still uses Network Solutions' website forms might end up with v=spf1 include:spf.protection.outlook.com include:spf.registeredsite.com ~all. Check what you actually send from before you keep or remove an include. The SPF Record Generator builds a merged record and counts lookups, and our SPF provider pages list each include.

How do you add a DKIM record in Network Solutions?

The DKIM record comes from whoever sends your mail. Network Solutions' DKIM article says its Cloud Mail and Standard Email users don't need to set up DKIM themselves, and points Google Workspace and Microsoft 365 customers to those providers' instructions.

DKIM as a TXT record

1. Click +Add Record and choose TXT.
2. Set Refers to to Other Host and enter the selector host, for example google._domainkey.
3. Paste the full key, starting v=DKIM1;, into TXT Value. Network Solutions says "You will need the entire TXT Value you were given."
4. Click Add.

Network Solutions' help doesn't document a length limit or splitting rules for TXT values at the time of writing (October 2026). If your provider shows a 2048-bit key as several quoted chunks, that's valid: RFC 6376, section 3.6.2.2 says the strings are joined "with no intervening whitespace." Check the result with the DKIM Checker, and see our guide to DKIM keys too long for a TXT record if it's cut short.

DKIM as CNAME records

Microsoft 365 and many sending platforms use CNAMEs.

1. Click +Add Record and choose CNAME.
2. Set Refers to to Other Host and enter selector1._domainkey as the Host Name.
3. Paste the provider's target into Alias to, without a trailing period.
4. Click Add, then repeat for selector2._domainkey.

Network Solutions says "CNAME records can only be created for third-level domains," so a CNAME can't sit on the root. That's fine for DKIM, which always uses a prefix. Then turn signing on in your provider's console: our DKIM setup guide for Microsoft 365 and Google Workspace shows where, and DKIM records by provider lists each service's selectors.

How do you add a DMARC record in Network Solutions?

Network Solutions' DMARC instructions use the standard format, v=DMARC1; p=none; rua=mailto:[user email], and recommend moving from none to quarantine to reject while you watch reports.

1. Click +Add Record and choose TXT.
2. Set Refers to to Other Host and enter _dmarc as the Host Name.
3. Enter your policy as the TXT Value, for example v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com.
4. Click Add.

Network Solutions notes the report address "must be under the domain you are managing" unless you publish an extra DNS record. That record is DMARC's external reporting authorization: RFC 9989, Appendix B.2 shows the receiving domain publishing a TXT record such as example.com._report._dmarc.thirdparty.example.net with the value v=DMARC1;. It goes on the receiving domain, not yours; our guide to DMARC rua and ruf addresses explains it. The DMARC Record Generator builds the record.

How do you change MX records in Network Solutions?

1. On the DNS tab, note your current MX records so you can roll back.
2. Click +Add Record and choose MX.
3. Set Refers to to @.
4. Enter the host in Mail Server, without a trailing period, and set Priority and TTL.
5. Click Add, and repeat for each further mail server.
6. Delete the old MX records through the vertical ellipsis once your new provider's instructions say to. Microsoft's instructions say to delete all other MX records when you move to Microsoft 365.

Network Solutions describes MX records simply: "Without MX records, a domain would be unable to receive email messages." Read how to change MX records without losing email first, and consider lowering the TTL a few hours ahead. The 2-hour default means resolvers can keep the old answer for that long; our TTL guide explains the timing.

What does a complete Network Solutions email setup look like?

An example for a domain on Microsoft 365. Your values will differ.

How do you check the records after saving?

Network Solutions says "Advanced DNS updates may take up to two hours to fully propagate." Then:

1. MX: MX Lookup shows only your new mail servers.
2. SPF: SPF Checker finds one record with 10 lookups or fewer.
3. DKIM: DKIM Checker finds a valid key at each selector.
4. DMARC: DMARC Checker parses your policy.
5. Headers: a test message to an outside mailbox shows spf=pass, dkim=pass and dmarc=pass. Our header reading guide shows where to look.

What are the common Network Solutions email DNS mistakes?

• Adding a second SPF record next to the existing spf.registeredsite.com one.
• Typing the full domain into Host Name. Use _dmarc, not _dmarc.example.com.
• Leaving a trailing period on an MX or CNAME target.
• Forgetting the 2-hour TTL when planning an MX cutover.
• Moving nameservers to Network Solutions without first copying email records from the old DNS host.

Next steps

1. Run the Email Health Check to see MX, SPF, DKIM and DMARC together.
2. Build records with the SPF Record Generator and DMARC Record Generator.
3. Moving mail between providers? Use the change email hosting provider checklist.
4. Keep an eye on changes: the free Domain Watch checks your public MX, SPF and DMARC weekly and emails you when they change.

If you add a filtering service such as iBlockSpam, the MX steps are the same with its mail servers as the values. More walk-throughs are in setup guides.