DNS Records for Irish Businesses: Website and Professional Email Setup
DNS connects a domain name to services such as a website and professional email. For an Irish business, the most useful records to understand are A, AAAA, CNAME, MX, TXT, SPF, DKIM, and DMARC. You do not need to memorise every DNS standard, but you should know which provider supplies each value and how to change records without interrupting service.
This guide uses a fictional domain, example.ie. Never copy its sample values into a live zone. Use the exact records supplied by your website, hosting, or email provider.
Nameservers and DNS records are different
Nameservers identify the system that hosts the authoritative DNS zone. DNS records are the entries inside that zone. Changing an A record can redirect a website while leaving email untouched. Changing nameservers delegates the entire zone and can affect the website, email, verification records, and subdomains at once.
Before changing nameservers, copy every record from the old DNS provider and recreate the required records at the new provider. A partially copied zone is a common reason a website works while email stops—or the reverse.
Website DNS records
A record
An A record points a hostname to an IPv4 address. The root of the domain is often represented by @. Your hosting provider may ask you to point example.ie to a server IP using an A record.
AAAA record
An AAAA record is the IPv6 equivalent of an A record. Add it only when the destination service provides a valid IPv6 address. An incorrect AAAA record can cause failures for visitors whose networks prefer IPv6 even when the A record is correct.
CNAME record
A CNAME makes one hostname an alias of another. A common setup points www.example.ie to a hostname supplied by the website platform. DNS providers generally do not allow a CNAME at the zone apex when it conflicts with other required records, although some offer flattened or ALIAS-style alternatives.
Professional email DNS records
MX records: where incoming mail goes
MX records tell sending mail systems which servers accept email for the domain. Priorities determine the preferred order: a lower number normally has higher priority. Enter the complete set given by the email provider and remove old MX records only when the new service is ready.
SPF: which systems may send
SPF is published as a TXT record. It identifies services authorised to send email for a domain. A domain should normally have one SPF policy at a hostname, not several separate v=spf1 records. When multiple services send mail, combine the mechanisms according to the providers’ documentation.
Do not add an email vendor to SPF unless it actually sends mail using your domain. Every unnecessary sender broadens the policy and makes maintenance harder.
DKIM: a cryptographic signature
DKIM allows the email service to sign outgoing messages. The public verification key is published in DNS under a selector supplied by the provider. Generate and enable DKIM in the email administration portal, publish the exact DNS record, and then confirm that the provider reports it as active.
DMARC: how receivers handle authentication failures
DMARC uses SPF and DKIM alignment to help receiving systems decide what to do when a message does not authenticate. It can also send aggregate reports to a monitored mailbox.
A cautious rollout starts with monitoring, reviews legitimate senders, and only then moves toward quarantine or rejection. Publishing a strict policy before every genuine sender is authenticated can cause valid invoices, booking confirmations, or support messages to be rejected.
A practical setup for a new Irish business domain
- Choose the authoritative DNS provider. Decide whether DNS will be managed through the registrar, hosting platform, or a specialist DNS service.
- Connect the website. Add only the A, AAAA, or CNAME values supplied by the website provider and test the root and www hostnames.
- Add the domain to the email provider. Complete its ownership-verification step before changing mail delivery.
- Publish the MX records. Compare the complete set and priorities against the provider’s current instructions.
- Configure SPF and DKIM. Account for every legitimate sending platform, including invoicing, newsletters, and support systems.
- Introduce DMARC carefully. Monitor reports, correct authentication gaps, and strengthen the policy when legitimate mail consistently passes.
- Test externally. Send and receive messages using an account outside the business domain, and inspect authentication results.
- Document the zone. Record who owns each entry and why it exists so future changes do not remove a live dependency.
DNS change safety checklist
- Export or record the current zone before editing.
- Verify that you are editing the authoritative DNS service, not an inactive copy.
- Use provider-supplied values rather than examples from a guide.
- Lower TTL in advance only when a planned migration requires it.
- Do not delete old records until the replacement service has been tested.
- Avoid duplicate SPF policies.
- Check both IPv4 and IPv6 behavior when AAAA records exist.
- Allow for cached DNS answers while validating a change.
How long do DNS changes take?
The authoritative provider can publish a change quickly, but recursive resolvers may keep the previous answer until its TTL expires. This is why different users can temporarily receive different answers. “Propagation” is not one universal timer; it depends on the previous TTL, the record type, and resolver caching.
Nameserver changes can take longer to appear consistently because delegation information is cached separately. Keep the old DNS zone available during a planned transition.
Common mistakes that break business email
- Replacing nameservers without copying MX and TXT records.
- Leaving old MX records active alongside a new provider.
- Publishing two SPF records instead of one combined policy.
- Turning on a strict DMARC policy before authenticating every legitimate sender.
- Deleting a DKIM selector still used by an email or marketing platform.
- Testing only outbound email and forgetting inbound delivery.
Website hosting and email do not have to be together
The domain registrar, DNS provider, web host, and email provider can be four different services. DNS is what connects them. Keeping a clear record of those relationships makes later transfers and incident recovery much easier.
Explore professional email options, review website hosting, or use the help centre when planning a DNS change. If the domain is moving between registrars, follow the .ie transfer checklist before changing nameservers.