[ DNS-provider guides ]

Publish and verify email authentication records in Network Solutions

Use the Network Solutions DNS editor without confusing registration with DNS hosting, overwriting a sender policy, or publishing authentication records at the wrong owner name.

By the EmailAuth research team · 7 min read

[ Key points ]

  • Verify the active service and authoritative DNS before editing.
  • Preserve record types, owner names and existing authorized services.
  • Verify public answers and actual aligned mail separately.
On this page
  1. Key points
  2. Takeaway
  3. By role
  4. Frequently asked questions
  5. Sources
  6. Glossary
  7. Related guides

[ Takeaway ]

Verify public answers and actual aligned mail separately.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Mail admin perspective on reproducible publication

Keep the editor input separate from the intended authoritative owner.

Next steps

  1. Preserve complete prior record sets.
  2. Check TXT boundaries and CNAME conflicts.
  3. Capture authoritative answers and the actual message identities.

CISO / SecOps

CISO perspective on DNS trust

Publishing a record delegates trust but does not prove a sender uses it correctly.

Next steps

  1. Review new sender authorization and reporting destinations.
  2. Keep independent verification and rollback ownership.
  3. Do not close the live, visual or SME gates from documentation alone.

Founder / Non-technical

Founder perspective on protecting domain services

Treat this as a narrowly scoped DNS change, not a registrar migration.

Next steps

  1. Name who may pause the affected send.
  2. Keep website and inbound mail changes outside the approved scope.
  3. Require a real workflow test before declaring completion.

[ FAQs ]

Frequently asked questions

Is Network Solutions necessarily my DNS host?

No. Check the authoritative nameserver delegation. Registration and DNS hosting may be in different services or accounts.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

Which Network Solutions SPF value should I use?

Use authorization for your actual sender. The provider’s hosting/contact-form example is not a universal policy for all registered domains.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

What belongs in the DMARC host field?

The published owner must be the applicable _dmarc name. Confirm how your current editor expands its host input and query the final authoritative owner.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

Can I add another SPF record for a new sender?

Do not publish two candidate SPF policies at the evaluated owner. Merge authorized sources into one valid policy and check its dependencies.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

Why can a DKIM CNAME conflict with a TXT record?

A CNAME owner has coexistence constraints. Resolve the active selector’s ownership and rotation plan before replacing a key with a delegation.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

Do displayed quotes mean the TXT value contains quotes?

Not necessarily. Inspect the returned DNS character strings and reconstructed value rather than copying display punctuation blindly.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

Does saving the record prove mail authentication works?

No. Verify authoritative publication, then inspect a received message from the actual workflow for passing aligned authentication.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

What evidence remains outstanding for this guide?

A current account walkthrough, visual host-entry check, authoritative before/after capture, independently received message and human SME approval remain required.

Network Solutions: manage DNS and advanced DNS records Network Solutions: manage SPF records SPF RFC 7208 DKIM RFC 6376 DMARC RFC 9989 DNS RFC 2181

[ Sources ]

Sources

  1. Network Solutions: manage DNS and advanced DNS records

    Sections CNAME284–319; TXT321–353; classic TXT355 onward

  2. Network Solutions: manage SPF records

    Sections Contact form-specific example39–43; account path45–52

  3. SPF RFC 7208

    Sections §3.2; 3.3; 4.6.4

  4. DKIM RFC 6376

    Sections §3.5; 3.6.2; 6.1

  5. DMARC RFC 9989

    Sections §4.4; 4.7; 4.10; 5

  6. DNS RFC 2181

    Sections §10.1 CNAME resource records

[ Glossary ]

Glossary

Authoritative owner
The exact DNS name whose record set the authoritative servers publish.
Relative host input
An editor label that may be expanded with the zone name.
TXT character string
One component of a TXT record, distinct from another separate record.
Selector conflict
Two services attempting incompatible use of the same DKIM owner.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base