SaaSTech Servers
Domain Portfolio

Domain account

Manage your domains.

Review DNS, renewals, forwarding, contacts, and domain settings in one place.Open Domain Portfolio Sign in to My AccountNeed help with DNS?
Start with your domainFind a new name or bring one you already own.
Choose a domain action
← Domain & DNS CentreHELP CENTRE

DNS, in plain language

Quick definitions, practical checks, and direct SaaSTech account instructions for common DNS tasks.

Use results as a check:Compare MXToolbox results with official provider instructions and your reviewed plan. A warning is a reason to investigate—not permission to delete records.
GLOSSARY

Common DNS terms

A record

Points a name to an IPv4 address, commonly used for a website’s root domain.

AAAA record

Points a name to an IPv6 address.

CNAME

Makes one hostname an alias of another. A CNAME normally cannot share the same host with other record types.

DNS

The system that translates domain names into destinations used by websites, email, and other services.

DKIM

A mail signature published in DNS that helps receiving systems verify outgoing email.

DMARC

A policy and reporting record that tells receivers what to do when SPF or DKIM checks fail.

Host / Name

The portion of the domain a record applies to. @ commonly means the root domain.

MX record

Directs incoming email. Lower priority numbers are usually preferred first.

Nameservers

Identify the provider that hosts the authoritative DNS zone.

Propagation

The period while DNS resolvers refresh cached information after a change.

SPF

A single TXT policy identifying systems allowed to send mail for a domain.

TTL

How long resolvers can cache a DNS answer before checking again.

TROUBLESHOOTING

Start with the symptom

Website changed, but email stopped+

Check that MX, SPF, DKIM, and DMARC records were preserved. If nameservers changed, compare the new zone with the dated backup.

The provider cannot verify my domain+

Copy the TXT host and value exactly, check whether the DNS manager automatically appends the domain, and allow the current TTL to pass.

The old website still appears+

Check both root and www records, wait through the old TTL, and test from a different network before editing again.

SSL or TLS is still pending+

Confirm the website records are correct and that conflicting CAA, proxy, or duplicate host records are not blocking certificate issuance.

Outgoing mail goes to spam+

Confirm there is one valid SPF record covering all senders, DKIM passes, and DMARC is configured appropriately.

I see duplicate or conflicting records+

Pause. Compare the host and type carefully, use the DNS Builder, and remove a record only when the provider explicitly requires replacement.

WHEN TO STOP

Protect the working services

Roll back or contact support when a critical website, email, payment, authentication, or customer service fails and the cause is not immediately clear.

Contact support · 800 987-3709