Skip to content
TECH Consult

DNS Explained for Businesses: A, MX and TXT Records

What DNS is, what each record in your domain's zone does, what propagation and TTL mean, and how to check your settings without breaking anything.

Published 10 min read

DNS is the part behind your domain that nobody notices until it breaks. Then the website won’t open, emails stop arriving or a new service refuses to start. Many companies have a DNS zone filled in by someone they can no longer reach, full of records nobody remembers the purpose of. Below you’ll find what DNS does, what each type of record means and how to check your domain’s settings without any risk.

What DNS does, in one example

Computers find each other by IP address, numbers like 203.0.113.10. People remember names, like company.ro. DNS (the Domain Name System) translates between the two.

Here’s what happens when a client types www.company.ro:

  1. Their computer asks their internet provider’s DNS server: “what’s the address of www.company.ro?”
  2. If that server doesn’t already know, it asks further: the root servers send it to the .ro registry, and the .ro registry sends it to the DNS servers for company.ro.
  3. The domain’s DNS servers give the answer: the IP address of your hosting server.
  4. The browser connects to that address and asks for the page.

The whole thing usually takes a fraction of a second. A server that wants to send you an email makes the same journey, except it asks for the MX record rather than the website’s address. The answer is kept for a while in the memory of the servers along the way, so the next question is faster.

Three different places: registrar, DNS servers, hosting

The most common confusion comes from the fact that the domain, the DNS and the hosting can live in three different places:

  • The registrar (for .ro domains, ROTLD, the registry that runs Romania’s .ro domain, or one of its partners) records who owns the domain and which DNS servers it uses.
  • The DNS servers (nameservers) hold the domain’s zone, the list of all its records. They can belong to the registrar, the hosting provider or a separate service.
  • The hosting is the server where the website and, usually, the email live.

When you want to change a record, you need to know where the DNS zone is. Editing the zone in a panel the domain doesn’t actually use has no effect at all, and it happens a lot. To find your domain’s DNS servers, look it up in WHOIS or use the command further down.

The records you’ll come across

A business DNS zone usually contains a handful of record types:

Type What it’s for Example
A The IPv4 address for a name company.ro → 203.0.113.10
AAAA The IPv6 address for a name company.ro → 2001:db8::10
CNAME A name that’s an alias for another name www.company.ro → company.ro
MX The server that receives the domain’s email company.ro → mail.company.ro
TXT Free text, used for SPF, DKIM, DMARC and verification v=spf1 ...
NS The domain’s DNS servers ns1.provider.ro
SRV Special services (for example automatic setup) _autodiscover._tcp

A few details that matter in practice:

  • The A record for the main domain and for www decides where the website opens. When you move hosting, this is the one you change.
  • MX records have a priority, a number. The server with the lowest number is tried first. If you have two MX records pointing to different servers that aren’t set up as backups for each other, some messages can go missing.
  • TXT records pile up over time: domain verification for Microsoft 365, for webmaster tools, for a newsletter service. Before you delete one, find out what uses it.
  • A CNAME can’t sit on the main domain (company.ro) alongside other records. That’s why the main domain uses an A record, while www can be a CNAME.

Subdomains

A subdomain, such as shop.company.ro or booking.company.ro, is just one more record in the same zone. It isn’t registered separately with ROTLD and costs nothing extra at the registry. It can point to the same server as the main site or to a completely different service, such as an online booking platform.

When an outside service asks you to add a subdomain, it usually gives you a CNAME record like booking → client123.platform.com. You add it to your DNS zone, and the service then issues the certificate for that name.

What DNS doesn’t do

DNS doesn’t redirect pages. A record can’t send company.ro/offer to another address and can’t turn http into https. Those are redirects done by the web server after DNS has finished its job. If you want a secondary domain, say your company’s old name, to lead to your main site, you need both: DNS pointing to a server, and a redirect set up on that server.

DNS and your company email

Email depends on DNS even more than the website does. Besides MX, which says where messages arrive, three TXT records decide whether the messages your company sends land in the inbox or in spam:

  • SPF lists the servers allowed to send email on behalf of the domain.
  • DKIM publishes the key used to check each message’s signature.
  • DMARC tells the receiving server what to do with messages that fail those checks and where to send reports.

The big email providers have started demanding them explicitly. Since February 2024, Gmail requires SPF or DKIM from all senders, and all three from anyone sending more than 5,000 messages a day. The setup details are in our article on business email going to spam.

Propagation and TTL: why changes don’t show up straight away

After you change a record, some people see the new version immediately and others only after a few hours. This is popularly called DNS propagation.

In reality, nothing “propagates”. Each intermediate DNS server keeps an answer for as long as the record’s TTL (Time To Live) says, in seconds. Only once it expires does it ask again and get the new value. A TTL of 3600 means one hour; 86400 means one day.

For changes to the DNS servers of a .ro domain, ROTLD states that propagation can take up to 24 hours.

Here’s how to use TTL in your favour: a few days before a planned change, lower the TTL to a few minutes. Once you’ve made and checked the change, raise it again. The steps are described in our guide to moving a website to a new host.

How to check your domain’s DNS

You don’t need any special tools. Windows has the nslookup command:

  1. Press Windows + R, type cmd and press Enter.
  2. For the website address: nslookup company.ro
  3. For the mail servers: nslookup -type=mx company.ro
  4. For TXT records (SPF, DMARC): nslookup -type=txt company.ro and nslookup -type=txt _dmarc.company.ro
  5. For the domain’s DNS servers: nslookup -type=ns company.ro

If you want to see what a particular server answers, rather than your own computer’s cache, add its address at the end, for example the domain’s own DNS server: nslookup company.ro ns1.provider.ro.

On macOS and Linux the equivalent command is dig, for example dig mx company.ro.

Save the results to a file before any change. When something stops working afterwards, compare what the server answers now with what it answered before. Most of the time the difference is a single line: a missing MX, an SPF record with one wrong letter, or an A record still pointing to the old IP.

If a colleague sees the new site and you still see the old one, the problem is probably your local cache. Running ipconfig /flushdns in Command Prompt clears Windows’ DNS cache.

Common DNS zone mistakes

  • Deleting an “unknown” record that turns out to be the Microsoft 365 verification or the DKIM key.
  • Two SPF records on the same domain. The standard allows only one; with two, the check fails. Every service goes into the same record.
  • A missing or extra trailing dot. Some panels want the full name ending in a dot (mail.company.ro.), others add it themselves. A record written the wrong way becomes mail.company.ro.company.ro.
  • Editing the zone in the wrong panel, as described above.
  • Records left over from abandoned services. A subdomain pointing at a platform where the company no longer has an account can be taken over by someone else who creates an account there with the same name. Delete the records for services you no longer use.
  • No copy of the zone. Before any change, export or copy the zone to a file. If something goes wrong, you can rebuild it in minutes.

DNS security

Here’s what that means in practice: someone gets into your domain account with a stolen password and changes only the MX record. The website keeps working, nobody notices anything, but every email from your clients goes to the attacker for several days. Precisely because the effect isn’t visible straight away, your domain account deserves the same care as the director’s email.

Whoever controls a domain’s DNS can send its website and email anywhere. Protect your registrar account and your DNS provider account like your bank account: a unique password, two-factor authentication where available, and access only for the people who need it.

.ro domains can also use DNSSEC, an extension that digitally signs DNS answers so nobody can forge them along the way. ROTLD has a dedicated FAQ section on it. It’s usually switched on by whoever runs your DNS servers, not from your own computer.

Frequently asked questions

Can I have my website with one provider and email with another?

Yes. The A record sends visitors to the website’s server, and MX sends messages to the mail server. The two can be with different providers, as long as the DNS zone is filled in correctly for both.

Why does the new site show on my phone but not on my computer?

Every device and every network has its own DNS cache. A phone on mobile data asks a different server from the office computer. Once the old record’s TTL expires, they all reach the same answer.

Where do I find my domain’s DNS zone?

With the provider whose DNS servers appear in WHOIS or in the output of nslookup -type=ns. If the servers belong to your hosting, the zone is in your hosting panel. If they belong to the registrar, the zone is in your domain account.

Which records does Microsoft 365 need?

Microsoft 365 usually asks for a TXT record to verify the domain, an MX pointing to Microsoft’s servers, their SPF, an autodiscover CNAME for automatic Outlook setup and two CNAMEs for DKIM. You’ll find the exact values in the Microsoft 365 admin centre under the domain settings, which also checks whether you’ve added them correctly.

Will changing DNS stop my email?

Only if you change the MX or move the DNS servers without recreating every record. Changing the website’s A record doesn’t affect email, as long as the MX doesn’t point to that same name.

For the link between a domain and hosting, how web hosting works gives a short explanation, and our guide to registering a .ro domain shows how to stay in control of your domain.

When to leave DNS to a technician

You can run nslookup checks any time, with no risk. Changes are worth leaving to someone who knows what each line does when the zone has many services, when you’re moving email, or when you’re setting up SPF, DKIM and DMARC for the first time. On TECH Consult web hosting we configure the DNS zone for your website and email, and for domains with email at another provider we help through IT maintenance.

Tell us what is not working

Describe the problem in a few lines. We reply with what we think needs doing and what it would cost.

Request a quote