CNAME, short for Canonical Name record, is a DNS record that does not create its own final destination, but instead says that one hostname is simply an alias of another hostname. In other words, instead of pointing a domain or subdomain directly to an IP address through an A or AAAA record, it first points to another hostname, and only that hostname is then resolved further. That is exactly why CNAME is often used where multiple names or subdomains should all lead to one main technical target.

At first glance, CNAME can seem like a small DNS shortcut. In reality, it plays an important role anywhere domain management needs to stay simple and administrators do not want to maintain the same IP address or the same destination server manually in several places. That is why CNAME is widely used with subdomains, CDN services, external SaaS tools and many hosted platforms.

What a CNAME record actually does in practice

When an A record is used, a domain or subdomain points directly to a specific IPv4 address.

With an AAAA record, the logic is the same for IPv6. CNAME works differently.

It does not say “this name goes to this IP address”. It says “this name is an alias of another name”.

That means the DNS lookup has to continue one step further. First, the resolver finds out which hostname the CNAME points to. Only then does it continue looking for the final IP address or other relevant DNS data connected to that target name. That is the real logic of CNAME – it does not define its own technical endpoint, but refers to another name that already has one.

How to think about CNAME in simple terms

A useful comparison is a public-facing brand name or a business nickname that leads to one central office. One name is the main one, and the other names simply point to it. That is very close to how CNAME works in DNS.

A subdomain does not need its own separate destination. It can simply say: if you are looking for me, follow that other hostname instead. This gives administrators an important practical advantage. If the real technical destination changes later, they do not need to update everything separately.

Why CNAME is used

The main benefit is simpler management. If several subdomains pointed directly to IP addresses and the target server changed, multiple records would need to be edited manually. With CNAME, administrators can keep the alias structure cleaner and reduce the number of places where changes must be made.

This is especially useful in environments where technical destinations change more often – for example with cloud services, CDNs, hosted applications or third-party platforms. That is why CNAME is not just a decorative DNS feature. It is a practical tool for keeping DNS setups cleaner and less error-prone.

CNAME does not point to an IP address

This is one of the most important things to understand. A CNAME record does not point to an IP address. It always points to another domain name or subdomain name. If the goal is to point directly to an IP address, the correct choice is an A record for IPv4 or an AAAA record for IPv6.

This is also where mistakes often happen. Some people expect CNAME to be just another way of sending traffic to a server. In reality, it serves a different purpose. It creates an alias from one name to another name.

Why CNAME should not exist alongside other records on the same name

This is another key property of CNAME. If a certain hostname has a CNAME record, that same hostname should not also have other normal DNS records such as A, MX or TXT on it. The reason is straightforward: CNAME says that the name is only an alias, not an independent place with its own separate set of DNS data.

In practical terms, this means that if a subdomain uses CNAME, it should not at the same time carry other unrelated DNS logic under the exact same name. That is why CNAME works best where a clean alias is really needed, not where multiple different DNS functions must coexist under one hostname.

Why CNAME matters in relation to MX records

In email infrastructure, one important rule is that an MX record should not point to a CNAME alias. Mail servers expect the MX target to be a real canonical hostname – in other words, a hostname that has its own A or AAAA record, not just another alias layer.

If this is configured incorrectly, the result can be compatibility problems or mail delivery issues. That is why, when working with MX records, administrators are usually told to use the real hostname of the mail server rather than a CNAME alias.

CNAME and the root domain

Another common question concerns the main domain itself, sometimes called the zone apex or root of the zone. This is where CNAME becomes problematic in standard DNS, because the main domain usually also needs core zone records such as NS and SOA. That does not fit with the idea of a pure alias.

In practice, this is why many DNS providers handle similar needs through provider-specific features such as flattening, alias-style behaviour or proxy layers. That is not the classic behaviour of a standard CNAME record itself, but rather a workaround implemented by a particular DNS platform.

Where CNAME is used most often

CNAME is commonly used for subdomains that should point to an external service or a shared technical target. Typical examples include a company blog, an online shop running on an external platform, a landing page managed in a marketing tool, a CDN endpoint or different kinds of SaaS integrations.

In these situations, the big advantage is that the administrator does not need to know or constantly track the exact IP address of the target system. It is enough for the alias to point to the correct hostname provided by the service.

What are the limits of CNAME?

Although CNAME is very useful, it is not a universal answer for every DNS situation. It is not suitable where several different DNS functions must coexist under the same name. It should not be used as the target of an MX record, and in standard DNS it is also not a clean fit for the apex of a zone where core records must already exist.

So CNAME makes excellent sense in the right context, but only there. If it is used where a fully independent hostname with its own records is expected, it can create operational confusion instead of simplifying things.

Why this term is worth understanding even outside technical roles

CNAME is a good example of the fact that DNS is not only about turning domains into IP addresses. It is also a system that can work with aliases and with a cleaner separation of logic between different names. That matters for website owners, marketers and content managers as well, because they often connect domains to external services and need those connections to be set up correctly.

If you understand what CNAME does, it becomes much easier to see why some services ask for an alias to their hostname, why they do not simply give you an IP address, and why some DNS combinations work perfectly while others create technical conflicts.

That is why CNAME is worth understanding even outside strictly technical professions. It may look like a small DNS detail, but it often sits right at the point where websites, subdomains and external services are connected together.

Related terms

• DNS – CNAME is one type of DNS record, and its role only makes full sense when the wider logic of DNS is understood.
• Hostname – the specific name of a server or service on the network, such as app.example.com or mail.example.com. CNAME is important here because it points to another hostname rather than directly to an IP address.
• A record – points directly to an IPv4 address and helps show how that differs from CNAME.
• AAAA record – similar to an A record, but for IPv6 rather than IPv4.
• Alias – an alternative name that does not have its own independent destination, but instead refers elsewhere. This is exactly the role CNAME plays in DNS.
• IP address – the numerical address of a server or device on a network. In the context of CNAME, it matters because CNAME does not lead directly to an IP address, but first to another hostname.
• MX record – important in relation to CNAME because MX should not point to an alias, but to the real hostname of a mail server.
• Nameservers – CNAME records are stored on authoritative nameservers and served from there to the rest of the internet.
• SPF, DKIM, DMARC – related email and verification records that show DNS is not only about website routing, but also about delivery, authentication and domain trust.

Direct mail is a form of direct marketing in which a business sends physical promotional material straight to a selected recipient by post. In practice, this usually means letters, postcards, catalogues, brochures, samples or other printed items delivered to a home or business address. The key idea is simple: instead of reaching people through mass media, the company communicates with them directly through a mailing list and a tangible piece of mail.

At first glance, direct mail can seem old-fashioned compared with email, paid ads or social media. In reality, it still plays an important role in modern marketing – especially where attention is scarce, competition in digital channels is high and businesses want a message to feel more personal, more physical and harder to ignore.

What direct mail actually does in practice

Direct mail is built around one practical goal: sending a specific message to a specific audience without relying on a broad public channel such as television, display advertising or organic social reach.

A company prepares a mailing list, defines the target group, creates a printed message and sends it directly to recipients. The message may be promotional, informational or transactional in tone, but in most cases it is designed to create some kind of response – for example a website visit, a purchase, a store visit, a phone call or a registration.

That is why direct mail is often grouped under direct marketing rather than general brand advertising. It is usually not meant only to “be seen”. It is meant to trigger action.

How direct mail is different from email marketing

This distinction matters in English. Direct mail usually refers to physical mail delivered by post. Email marketing is a separate digital channel, even though both belong to the wider family of direct marketing.

The logic is similar in both cases: a message goes directly to a chosen recipient rather than being broadcast to a general audience. But the practical differences are significant.

• Direct mail is physical, slower, more expensive and often more noticeable.
• Email marketing is digital, faster, cheaper and easier to automate at scale.

That is why the two should not be treated as interchangeable terms, even if they are sometimes mixed together in less precise marketing language.

Why businesses still use direct mail

Direct mail remains useful because physical communication still stands out. In a world where people are flooded with digital messages every day, a printed item can feel more deliberate and more difficult to ignore than another email or banner ad.

It also creates a different kind of attention. A letter, postcard or printed offer is tangible. It can sit on a desk, be picked up later, be shown to another person or simply create a stronger impression because it exists in the physical world rather than disappearing in a crowded digital feed.

That does not mean direct mail is automatically better than digital channels. It means it works differently. Its strength is often in visibility, memorability and perceived seriousness rather than in speed or low cost.

What direct mail is usually used for

Direct mail is commonly used where a business wants to reach a selected audience with a clear message and a strong call to action.

Typical use cases include:

• new customer acquisition in a defined area or segment,
• special offers and discount campaigns,
• catalogues and product launches,
• event invitations,
• membership or donation appeals,
• reactivation of former customers,
• high-value B2B outreach where a physical message can stand out more than a standard email.

In many organisations, direct mail works best not as a standalone tactic, but as part of a broader campaign together with a landing page, QR code, personalised URL, follow-up email or phone contact.

What makes direct mail effective

Good direct mail is rarely just “a printed ad sent to many people”. Its effectiveness depends on targeting, timing, relevance and clarity.

In practical terms, the strongest campaigns usually get four things right:

• the audience – the mailing list is relevant and reasonably clean,
• the offer – the recipient quickly understands why the message matters,
• the format – the design, envelope, copy and layout support the message instead of burying it,
• the action – the recipient knows exactly what to do next.

That is why direct mail is not only a print question. It is also a data, copywriting and campaign-structure question. A weak offer in a beautiful envelope is still a weak offer.

What direct mail can do better than some digital channels

Direct mail has some obvious disadvantages, especially cost and speed, but it also has strengths that digital channels do not always match.

It can feel more premium. It can be harder to ignore. It can reach people who are overloaded by digital communication. And in some audiences – especially older or more traditional segments – it may feel more trustworthy than yet another marketing email.

It is also less exposed to some of the immediate clutter of digital platforms. A letterbox is not the same environment as a social feed or an inbox with hundreds of unread messages. That alone can make the message easier to notice.

What are the limits of direct mail?

Direct mail is useful, but it is not efficient for everything. It is slower than email, more expensive to produce and distribute, and less flexible if something needs to be changed at the last minute.

It also depends heavily on data quality. If the mailing list is poor, outdated or badly segmented, the campaign becomes expensive very quickly. And unlike email, printed mail is not something you can adjust instantly after launch.

Measurement can also be more difficult. It is possible to track results through codes, personalised landing pages, QR codes or response channels, but the attribution is often less immediate than in digital media.

Where legal and compliance issues enter the picture

Direct mail is not only a creative or operational channel. It also involves personal data, contact selection and marketing rules. For an EU audience, that means the legal side should never be treated casually.

Where direct mail involves personal data, organisations need a lawful basis for using that data and must respect data protection principles such as transparency, relevance and the right to object to direct marketing. If email is involved instead of physical mail, additional electronic marketing rules come into play under the ePrivacy framework and national law. That is why businesses should be careful not to treat “direct marketing” as one legally identical activity across every channel.

In practical terms, postal direct mail and email marketing may sit under the same broad marketing idea, but they do not always work under exactly the same compliance logic.

Why direct mail still matters in modern marketing

Direct mail still matters because marketing is not only about using the newest channel. It is about using the channel that fits the audience, the message and the buying context.

For some campaigns, email will clearly be the better choice. For others, especially when memorability, local targeting, perceived seriousness or a tangible brand experience matters, direct mail can still be a very strong option.

Its role is often strongest when it works together with digital channels rather than against them. A printed piece can drive someone online, support a sales conversation, reinforce a campaign they have already seen elsewhere or help a message stand out in a more personal way.

Why this term is worth understanding even outside marketing teams

Direct mail is a useful concept because it shows that direct marketing is not only a digital topic. Businesses still communicate through physical channels when those channels fit the objective better.

If you understand what direct mail really means, it becomes easier to separate it from email marketing, to evaluate whether it makes sense for a campaign and to avoid the common mistake of treating every one-to-one marketing message as the same thing just because it is “direct”.

That is why direct mail still matters beyond specialist marketing jargon. It is one of the clearest examples of how channel choice changes the whole logic of a campaign – from cost and speed to attention, trust and response behaviour.

Related terms

• Direct marketing – the wider marketing category to which direct mail belongs.
• Email marketing – a related but separate direct channel that works digitally rather than through physical mail.
• Mailing list – the database or selected set of recipients used for a direct mail campaign.
• Segmentation – important because direct mail becomes expensive quickly if it is sent to the wrong audience.
• Call to action – the next step the recipient is meant to take after receiving the message.
• A/B testing – often used in campaign optimisation, although easier to run in digital channels than in physical mail.
• Lead generation – one of the common commercial goals of direct mail.
• Response rate – one of the key ways direct mail campaigns are evaluated.

IPv6 is the newer version of the Internet Protocol used to identify devices and services on networks and on the internet. It was introduced mainly because the older IPv4 system no longer provided enough addresses for the long-term growth of the internet. In practical terms, IPv6 serves the same basic purpose as IPv4 – it gives devices a network address so data can be delivered to the correct destination – but it does so with a much larger address space and a different address format.

At first glance, IPv6 can seem like a purely technical topic that only matters to network engineers or hosting providers.

In reality, it is part of the wider infrastructure behind modern websites, cloud services, hosting platforms, email systems and internet connectivity. Many users never notice it directly, but it increasingly matters wherever services are meant to be reachable in a modern internet environment.

What IPv6 is in the simplest possible way

The easiest way to think about IPv6 is as a newer and much larger addressing system for the internet.

Every device or service that communicates over a network needs an address. Without that address, the network would not know where to send the data. IPv6 provides those addresses.

Its role is therefore not exotic or optional in principle. It is one of the ways the internet identifies real destinations. The reason people hear about it mainly now is that the older IPv4 system was built in a much earlier stage of internet growth and eventually became too limited for the number of connected devices and services the world now needs.

Why IPv6 was introduced

The most important reason is address space.

IPv4 uses a 32-bit address system. That was enough in the early years of the internet, but it is not enough for a world full of websites, mobile devices, cloud platforms, smart devices, data centres and constantly growing internet connectivity.

IPv6 uses a 128-bit address space instead. In practical terms, that means vastly more possible addresses. This is the core reason IPv6 exists. It was not introduced because IPv4 suddenly stopped working, but because the long-term future of the internet needed a much larger addressing system.

What an IPv6 address looks like

An IPv6 address looks very different from an IPv4 address.

An IPv4 address typically looks like this:

• 192.0.2.1

An IPv6 address typically looks like this:

• 2001:db8::1

The difference is immediately visible. IPv6 addresses are longer, written in hexadecimal notation and separated by colons rather than dots. They can also use shortened notation rules, which is why one IPv6 address can sometimes be written in a shorter or more compressed way than beginners expect.

For a non-technical reader, the key point is not memorising the exact format. It is understanding that IPv6 addresses look different because they belong to a completely different addressing system from IPv4.

How IPv6 is different from IPv4

IPv6 and IPv4 solve the same broad problem, but they do it in different ways.

• IPv4 uses 32-bit addresses and the familiar dotted-decimal format.
• IPv6 uses 128-bit addresses and a hexadecimal format with colon separators.

In practical terms, that means IPv6 offers far more available addresses and was designed with a more modern internet in mind.

That does not mean IPv6 instantly replaces IPv4 in every environment. In real-world infrastructure, both versions often exist side by side. This is commonly called dual-stack operation. A service can be reachable through IPv4, IPv6 or both.

How IPv6 relates to DNS

People do not usually type IP addresses directly into the browser. They use domain names and hostnames instead. That is where DNS becomes important.

For IPv6, the DNS record type used to publish the address is the AAAA record. That is the equivalent of the A record used for IPv4.

So if a service should be reachable over IPv6, DNS needs to publish its IPv6 address through an AAAA record. Without that record, the server may technically support IPv6, but the DNS system will not reveal that address to users or applications in the standard way.

Why IPv6 does not automatically mean everything will work better

This is an important practical point.

The presence of IPv6 does not automatically make a service faster, better or more reliable by itself. For IPv6 connectivity to work properly, the whole path needs to be ready for it – the server, the network, the firewall, the application and the DNS configuration.

If an IPv6 address is published but the service does not respond correctly over IPv6, the result can be availability problems or connection delays. That is why IPv6 should not be enabled only “for appearance”. It makes sense when the surrounding infrastructure is genuinely ready.

Where IPv6 is used most often

IPv6 appears in many modern network and service environments, especially where long-term internet readiness matters.

Typical examples include:

• web hosting and websites,
• API services,
• cloud infrastructure,
• modern hosting providers,
• mail infrastructure,
• mobile and ISP networks,
• enterprise and internal networks that are being modernised.

In some environments, IPv6 is already a normal part of standard deployment. In others, it still appears mainly during audits, migrations or infrastructure upgrades.

What about private or internal IPv6 use?

IPv6 is not only for globally reachable public internet addresses. There are also address types used in more limited scopes.

One important example is Unique Local Addresses, often shortened to ULA. These are intended for local communications and are not expected to be routed on the global public internet. In practical terms, they are one of the ways IPv6 can be used for internal addressing in a more limited environment.

This matters because IPv6 is not just “a public internet technology”. Like IPv4, it also has internal network use cases, although the technical details are not identical.

Why IPv6 and IPv4 often exist together

In real infrastructure, IPv6 does not usually appear by completely replacing IPv4 overnight.

Instead, many environments run both at the same time. That is because large parts of the internet, applications, providers and customer networks still rely on IPv4, while newer systems increasingly support IPv6 as well.

This dual existence is one of the reasons why DNS and hosting setups often include both A and AAAA records. It is not duplication by mistake. It is a practical way to make the same service available through both address families.

How IPv6 relates to hostnames and nameservers

IPv6 does not replace hostnames. Users still work with names such as www.example.com or api.example.com. Those names are then resolved through DNS.

The actual DNS data, including the AAAA record for IPv6, is stored on the authoritative nameservers of the domain. That is where resolvers look when they need to find the IPv6 address tied to a hostname.

So even though IPv6 is a networking concept, it still depends heavily on the surrounding DNS infrastructure to become useful in everyday internet operation.

What happens if a service has no IPv6 support?

If a service has no IPv6 support, that does not automatically mean it will stop working. In many cases, it will still be fully reachable over IPv4.

However, if the goal is full modern reachability, future-proofing or support for environments that prefer or expect IPv6, then the absence of IPv6 becomes more important. That is why IPv6 increasingly matters as part of infrastructure maturity, even if not every service depends on it equally today.

What are the limits of IPv6 as a concept?

IPv6 is essential for the long-term growth of internet addressing, but it is not a universal shortcut that solves every network problem on its own.

It does not automatically fix poor application design, broken DNS, weak hosting, slow servers or bad security practices. It solves the addressing problem in a more scalable way. That is a very important improvement, but it is still only one layer of the broader internet stack.

Why this term is worth understanding even outside technical roles

IPv6 is a good example of the fact that the internet is not static. It evolves in response to scale, infrastructure demands and long-term technical limits.

For website owners, hosting administrators, founders and digital teams, understanding IPv6 helps explain why services may have both A and AAAA records, why some audits mention IPv6 readiness, and why a modern service can be reachable in more than one network way at the same time.

Once the concept is clear, it also becomes easier to understand that internet availability is not only about “having a website online”. It is also about whether the addressing, DNS and network path are ready for the environments in which users actually connect.

That is why IPv6 matters even outside specialist networking roles. It is one of the clearest examples of how internet infrastructure adapts to long-term growth – and why modern services often need to be thought about in more than one addressing layer.

Related terms

• DNS – IPv6 becomes practically usable through DNS because hostnames need to be translated into real network addresses.
• IPv4 – the older addressing system that IPv6 complements and gradually supplements.
• AAAA record – the DNS record type that maps a hostname or domain to an IPv6 address.
• A record – the equivalent DNS record type used for IPv4.
• IP address – the broader concept to which both IPv4 and IPv6 belong.
• Hostname – the name users work with before DNS resolves it to an IPv6 address.
• Nameservers – the authoritative servers that publish AAAA records and other DNS data connected to IPv6-capable services.
• Dual-stack – the common real-world setup in which both IPv4 and IPv6 are supported at the same time.

SPF, short for Sender Policy Framework, is a DNS record that allows a domain owner to say which servers are allowed to send email on behalf of that domain. In practice, it is one of the basic technical pillars of email trust and deliverability, because the receiving side can check whether a message came from an authorised source or from a foreign server only pretending to use the domain.

Put simply, SPF is a list of permitted sending sources. If an email arrives from somewhere else, that is a warning signal for spam filters and receiving systems that the message may not be legitimate.

At first glance, SPF can look like one more hidden DNS detail that only matters to mail administrators. In reality, it matters to any business or website that sends email from its own domain. As soon as a company uses normal staff mailboxes, a newsletter tool, a CRM, a webshop, a billing system, Google Workspace, Microsoft 365 or another sending platform, SPF becomes part of the domain’s real email infrastructure.

What SPF actually checks

This is one of the most important things to understand. SPF does not mainly check the address the ordinary recipient sees in the From field. Instead, it checks the technical sending identity used during SMTP delivery – most often the MAIL FROM domain, also commonly associated with the Return-Path.

That matters because many people assume SPF directly protects the visible From address on its own. That is not fully correct. SPF is valuable, but by itself it does not authenticate the visible sender identity in the way many non-technical users first imagine. That is one of the reasons why SPF is normally discussed together with DKIM and DMARC.

In practical terms, SPF answers a very specific question: Was this server allowed to send email using this domain as the envelope sender identity? That is already extremely useful, but it is still only one layer of email authentication.

Why SPF matters

SPF matters because email is easy to forge at the visible level. Without technical checks, attackers can try to send messages that appear to come from a real company domain even when the sending server has nothing to do with that company.

A properly configured SPF record helps in several ways:

• it limits domain spoofing – an attacker cannot freely use your domain from any random server without creating a technical mismatch,
• it improves trust signals – receiving systems can see that your domain has at least one basic authentication layer properly declared,
• it supports deliverability – SPF is no longer an optional bonus for serious senders, but a basic technical expectation,
• it makes troubleshooting easier – when mail fails, SPF helps narrow down whether the issue is caused by an unauthorised sending source.

One important clarification: SPF alone does not guarantee inbox placement. It is an important signal, but it works alongside other factors such as DKIM, DMARC, IP reputation, complaint rates and overall mailing quality.

What an SPF record looks like

SPF is normally published in DNS as a TXT record. A simple example may look like this:

v=spf1 ip4:203.0.113.10 include:_spf.google.com include:spf.mailprovider.example -all

At first sight, that string can look confusing, but the individual parts follow clear logic:

• v=spf1 – declares that this is an SPF record in SPF version 1 format,
• ip4:203.0.113.10 – allows a specific IPv4 address to send mail,
• include:_spf.google.com – includes the sending policy of another service, such as Google Workspace,
• include:spf.mailprovider.example – allows another external provider to send on behalf of the domain,
• -all – says that all other sending sources should be treated as not authorised.

That is why SPF is best understood as a structured policy rather than as one yes-or-no switch. It tells receiving systems which technical sources are allowed, and what attitude they should take towards everything else.

The SPF mechanisms people see most often

In real setups, a few SPF elements appear again and again:

• ip4: – allows a specific IPv4 address or range,
• ip6: – allows a specific IPv6 address or range,
• include: – imports the SPF policy of another provider,
• a – allows the IP address resolved from the A record of the domain or hostname,
• mx – allows the IP addresses of servers listed in the domain’s MX records.

And then there are the qualifiers at the end:

• ~all – softfail, a softer signal that other sources are not expected to be legitimate,
• -all – hard fail, a stronger statement that other sources are not authorised,
• ?all – neutral, which usually does not help very much in practice,
• +all – effectively allows everything, which defeats most of SPF’s practical purpose.

In day-to-day operations, ~all is often used during transition or cleanup phases, while -all is used when the sending infrastructure is already well mapped and controlled.

How to build SPF in real life

The practical setup process is usually straightforward in theory, but often messy in reality.

A sensible approach is usually this:

• list every system that sends email on behalf of your domain,
• check what each provider requires – some give IP addresses, others require an include: mechanism,
• combine everything into one SPF record, because one domain should have one effective SPF TXT policy,
• publish that record in DNS,
• test with real messages as well as DNS-level validation.

The biggest problem is usually not adding the record itself. It is forgetting one of the systems that sends mail for the domain. Companies often think only about normal employee mailboxes, but email may also be sent by a webshop, contact forms, invoicing software, CRM workflows, marketing tools, helpdesk systems or another automated platform.

If one of those senders is missing from SPF, its mail may start looking unauthorised even though the business itself genuinely uses that service.

Examples of SPF records and what they mean

Simple SPF for one IP address
v=spf1 ip4:203.0.113.10 -all

This means only that one server is authorised to send mail for the domain. Everything else should be treated as unauthorised.

SPF for Google Workspace and one mailing platform
v=spf1 include:_spf.google.com include:spf.example-newsletter.com -all

This means Google and the specified email platform may send on behalf of the domain.

A more cautious transition version
v=spf1 include:_spf.google.com ~all

This means Google is authorised, while other sources are treated as suspicious rather than firmly rejected. This is often used when a domain owner is still verifying whether every legitimate sender has already been included.

The most common SPF mistakes

SPF usually goes wrong in a few predictable ways:

• there are multiple SPF TXT records trying to act as separate SPF policies for the same domain,
• a legitimate sender is missing, often after a new CRM or marketing tool is added,
• old services remain in the record long after they stopped being used,
• the record becomes too complex and relies on too many external lookups,
• subdomains are ignored even though sending also happens from a dedicated mail subdomain,
• +all is used, which weakens the whole point of SPF.

Another practical mistake is expecting SPF to solve identity problems that belong to DKIM or DMARC. SPF is useful, but it was never designed to solve every email trust problem by itself.

What SPF does not solve

SPF is important, but it does not answer everything.

By itself, SPF does not tell you:

• whether the message content is relevant or wanted,
• whether the sender has a good reputation,
• whether recipients actually want these emails,
• whether the visible From address fully matches the authenticated identity the way a business may expect,
• whether a forwarded message will preserve the same technical behaviour.

That is exactly why SPF is usually discussed together with DKIM and DMARC. SPF helps answer whether the sending server was authorised. DKIM helps prove message integrity and domain-based signing. DMARC then adds policy and alignment around the visible sender identity.

How SPF relates to DNS, nameservers and mail routing

SPF only works because it is published in DNS and served by authoritative nameservers. That means SPF is not an isolated email switch. It is part of the wider DNS configuration of the domain.

It is also useful to understand what SPF is not. It is not the same as an MX record. MX records handle where incoming mail should be delivered. SPF, by contrast, describes which servers are allowed to send mail for the domain.

And it is not the same as a CNAME alias either. SPF is a TXT-based policy record, not an alias from one hostname to another.

Why this term is worth understanding even outside technical roles

SPF is one of those terms that many people only meet when emails start landing in spam or when a domain is being protected more seriously. Yet it is one of the clearest examples of how email trust depends on the technical layer behind the message, not only on the wording the recipient sees.

If you understand what SPF does, it becomes much easier to understand why one platform can send successfully while another suddenly fails, why adding a new mailing service affects deliverability, or why a company domain can be technically spoofed if authentication is weak.

That is why SPF matters not only to mail administrators, but also to marketers, founders, e-commerce operators and anyone whose business relies on email sent from its own domain. It is a quiet DNS record, but one of the most important ones in everyday email infrastructure.

Related terms

• DNS – SPF is published as a DNS TXT record, so its role only makes full sense within the broader logic of DNS.
• Nameservers – SPF records are stored on authoritative nameservers and served from there to the rest of the internet.
• TXT record – the DNS record type normally used to publish SPF.
• MAIL FROM / Return-Path – important because SPF mainly checks the SMTP envelope identity, not the visible From header.
• MX records – useful for contrast, because MX handles incoming mail routing, while SPF defines authorised outgoing sending sources.
• CNAME – another DNS record type, but with completely different purpose from SPF.
• DKIM – a related authentication method that signs email cryptographically and works alongside SPF.
• DMARC – the policy layer that builds on SPF and DKIM and helps connect authentication to the visible sender domain.

An AAAA record is a DNS record that maps a domain or hostname to a specific IPv6 address. It works in a similar way to an A record for IPv4, but instead of the older four-part address format, it uses the newer IPv6 format. So if a domain or service is meant to work over IPv6, the AAAA record is what tells the internet which address it should connect to.

At first glance, an AAAA record can seem like a narrow technical detail that only matters in more modern network environments.

In reality, it is an important part of the internet’s transition to IPv6. As soon as a server, application or online service supports IPv6, that information is normally published in DNS through an AAAA record.

What an AAAA record actually does in practice

When someone opens a website, or when an application connects to a service, the device first needs to learn which network address it should actually send the request to.

If the target server is available over IPv6, DNS can return an AAAA record. That record contains the exact IPv6 address the client should use.

This means the AAAA record itself does not “run the website” or “start the server”. It is a routing record in DNS that tells the internet which IPv6 address belongs to the given name.

Why it is called AAAA

The name AAAA often feels confusing because it does not sound intuitive at first.

The reason is historical. An A record is used for IPv4 addresses. The AAAA record was introduced as its equivalent for IPv6, which uses a much larger address space. In practical terms, though, the important point is not the name itself. The important point is that AAAA does not mean a “better A record”. It means a different DNS record type for a different kind of IP address.

What an AAAA record looks like

While an A record points to an IPv4 address such as 192.0.2.1, an AAAA record points to an IPv6 address, for example:

• 2001:db8::1

This is where the difference is easiest to see. IPv6 addresses are longer, written in hexadecimal form and use colons instead of dots. So the AAAA record is not different in what it fundamentally does. It is different in the type of address it publishes.

What is the difference between an A record and an AAAA record?

The core difference is simple.

• A record maps a name to an IPv4 address.
• AAAA record maps a name to an IPv6 address.

So both record types solve the same kind of task – translating a name into a network address – but each one does it for a different version of the Internet Protocol.

In practice, both records can exist on the same domain at the same time. That is common with services that should be reachable over both IPv4 and IPv6. The client or network environment then uses the version that is available and appropriate in that situation.

Why a domain can have both an A record and an AAAA record at the same time

This is a normal and correct setup in many real environments.

If a server is meant to support both protocols, DNS can publish both an A record and an AAAA record. That allows older environments to continue using IPv4, while newer or IPv6-capable environments can use IPv6.

This is not a conflict. On the contrary, it is one of the standard ways to make a service available to the widest possible range of users and networks.

That is also one of the ways in which AAAA differs from records such as CNAME, which follow a different logic and different usage rules.

Why an AAAA record does not automatically mean everything will work over IPv6

The mere presence of an AAAA record does not automatically mean the service will work correctly over IPv6.

For that to be true, the server itself, the network path, the firewall and the actual service all need to be ready for IPv6 as well. If an IPv6 address is published in DNS but the server does not respond properly on that address, the result can be availability problems or unnecessary connection delays.

That is why an AAAA record should not be added only “just in case”. It makes sense when IPv6 is genuinely ready at the infrastructure level too.

Where AAAA records are used most often

AAAA records are used wherever a service should be available over IPv6.

Typical examples include:

• web servers,
• API services,
• application servers,
• mail infrastructure,
• cloud platforms and modern hosting environments.

In some setups, the AAAA record is a routine part of standard DNS configuration. In others, administrators only encounter it when they start dealing with IPv6 connectivity, dual-stack operation or network audits.

How an AAAA record relates to a hostname

Like other address-type DNS records, an AAAA record is always tied to a specific name – in other words, to a domain or hostname.

That means an AAAA record does not belong to a server “in general”. It belongs to a specific name. For example, www.example.com may have one AAAA record, while api.example.com may have another. This is how DNS distinguishes which service should lead to which technical destination.

So the user usually does not deal directly with the IPv6 address itself. They work with the hostname, and DNS decides whether there is an A record, an AAAA record or both.

How an AAAA record relates to nameservers

The AAAA record is stored on the authoritative nameservers of the domain, just like other DNS records.

That is where DNS resolvers look it up before returning the answer to users or applications. So when an AAAA record changes, the new value does not become visible everywhere immediately. Like other DNS changes, it appears gradually as caches expire and resolvers fetch the new version.

What happens if an AAAA record is missing?

If a service has no AAAA record, that does not automatically mean it will not work at all. It means, however, that it will not be reachable over IPv6 through standard DNS resolution.

In many environments, that is not a critical problem as long as IPv4 is still available and there is an A record. But if the goal is full service reachability in networks that prefer or require IPv6, the absence of an AAAA record becomes relevant.

That is why AAAA is most important where the goal is proper modern network availability rather than only minimal fallback access.

Why this term is worth understanding even outside technical roles

The AAAA record is a good example of the fact that DNS is not only about one “internet address”. In reality, the same service can be published through more than one network path and more than one protocol version.

This matters even for website owners, hosting administrators and business operators who do not want to go deep into network engineering. Once you understand that A and AAAA records perform a similar role for different address families, it becomes much easier to understand why one service may be reachable in one way but not in another.

That is why the AAAA record is worth understanding outside purely technical roles as well. It is a small DNS detail on the surface, but an important part of how modern network availability actually works.

Related terms

• DNS – the AAAA record is one type of DNS record, and its role only makes full sense in the wider context of DNS.
• IPv6 – AAAA is specifically designed for IPv6 addresses, so the meaning of the record is closely tied to IPv6 itself.
• A record – the direct counterpart to the AAAA record for IPv4 and the clearest comparison for understanding the difference between the two address families.
• IP address – the AAAA record translates a name into a specific IPv6 address, which is one form of IP address used in networking.
• Hostname – the AAAA record belongs to a specific hostname or domain and defines which IPv6 address belongs to it.
• Nameservers – AAAA records are stored on authoritative nameservers and served from there to the rest of the internet.

An IP address is the numeric address of a device, server or other network endpoint. It is the technical identifier the internet uses to decide where a request should really be delivered. So when someone enters a website address or when two devices connect to each other, the communication ultimately depends on an IP address in the background. Without it, you could know the name of the domain or service, but you would still not know which exact technical destination should receive the connection.

At first glance, an IP address can seem like a purely technical detail that only matters to server or network administrators.

In reality, it sits behind almost every website load, email transfer and connection between devices on a network. Most users do not see it, because they work with a domain name or a service name instead. But whenever a real connection happens, the network still needs an IP address.

What an IP address is in the simplest possible way

The easiest way to think about an IP address is as the exact street address of a house.

The name of a company or a restaurant does not, by itself, tell you where it is physically located. You need the actual address. The internet works in a similar way. Domains and hostnames are names that people can remember easily. The IP address is the exact numeric value that tells the network where the request should really go.

So when you type a website address into the browser, the system first looks up the matching IP address through DNS. Only then can the connection to the server begin.

Why a domain or hostname is not enough on its own

A domain and a hostname are much more convenient for people than a string of numbers.

But for network traffic, the name alone is not enough. It is only a label. To make a real connection, that name has to be translated into a specific IP address.

That is why domains, hostnames and IP addresses are so closely related. The user enters the name, DNS looks up the IP address, and only then does the network know the real destination.

What an IP address looks like

In everyday practice, there are two main versions of IP addresses.

The first is IPv4, the older and still very widely used format. It looks like this:

• 192.168.1.1

The second is IPv6, which was introduced largely because the number of available IPv4 addresses could no longer meet long-term global demand. An IPv6 address may look like this:

• 2001:0db8:85a3:0000:0000:8a2e:0370:7334

For a non-technical user, the most important thing is simply that both versions serve the same basic purpose – to identify the destination in network communication.

What is the difference between a public IP address and a private IP address?

Not every IP address is visible directly from the internet.

A public IP address is one through which a device or service can be reached from outside the local network. This is what matters for public-facing websites, internet services and connections that need to be accessible from the wider internet.

A private IP address, by contrast, is used inside a local network – for example at home or in an office. These are the addresses typically used by routers, laptops, printers, smart TVs and other internal devices. They are not normally reachable directly from the public internet, because external communication usually passes through the public IP address of the router or network gateway.

In IPv4, the classic private address ranges are defined separately from the public internet space. That is why a device can have one internal private address inside a local network while the whole local network appears to the wider internet through a different public IP address.

An IP address is not the same thing as DNS

This is one of the most common points of confusion.

DNS is the system that translates names into technical data. An IP address is the actual numeric data the name is translated into.

In other words, DNS is the translation layer, while the IP address is the result the network needs for the real connection. When someone says that “DNS points to a server”, what they usually mean is that a DNS record translates the domain or hostname into the IP address of that server.

An IP address is not the same thing as a hostname

It is just as important to separate an IP address from a hostname.

A hostname is the name of a server or service, such as mail, api or www. The IP address is the numeric value that hostname is then resolved to.

So the hostname is the human-readable name, while the IP address is the network-level identifier. They are closely related, but they are not interchangeable.

Where IP addresses are used in practice

IP addresses are used almost everywhere network communication takes place.

This includes:

• loading websites,
• sending and receiving email,
• connecting devices in a home or business network,
• server infrastructure,
• cloud services,
• firewalls and access filtering,
• diagnostics and logging of network activity.

In many situations, the user does not notice the IP address at all. In others, it becomes critically important – for example when changing hosting, editing DNS records, troubleshooting email, restricting access by network address or analysing a connectivity problem.

How an IP address relates to websites and hosting

When a domain points to a web hosting service, what that usually means in practice is that a DNS record points to the IP address of the server where the website is stored.

That is why IP addresses often come up when changing hosting, migrating a website or editing DNS records. If the domain still points to the old IP address, users will still be sent to the old server. If it points to the new one, the traffic will start going elsewhere.

This is one of the reasons why changing the server alone is not enough. If the DNS path is not also updated to the correct IP address, users simply will not reach the new website.

How an IP address relates to email

An IP address also matters in email, even if not always as visibly as with websites.

When email is delivered, the sending system first uses the MX record to find the hostname of the mail server. That hostname is then resolved further to an IP address. That is why, in email operations, it matters not only which server name appears in the MX record, but also whether that hostname resolves to a working and correctly configured IP address.

This is another good example of how the domain name, the hostname and the IP address work together rather than replacing one another.

Why an IP address can change

Not every IP address is permanent.

Some addresses are fixed, or static. Others are dynamic and may change over time – this is common with ordinary consumer internet connections. This matters especially when something depends directly on the IP address, such as DNS records, firewall rules, access restrictions or a service configuration.

That is also why, in internet practice, people often prefer to work with domains and hostnames while letting a properly configured DNS system handle the changing IP addresses in the background.

What are the limits of an IP address as a concept?

An IP address is essential, but it does not tell you everything by itself.

It tells the network where to send the traffic, but it does not tell you what exact website, app logic or user account is behind that traffic. One IP address may host many services, and one service may use several IP addresses depending on the infrastructure.

That is why an IP address is best understood as a routing destination, not as a full explanation of everything a service is or how it behaves.

Why this term is worth understanding even outside technical roles

IP address is one of those terms almost everyone has heard, but relatively few people stop to think about what it really means.

Yet it shows very clearly the difference between how humans experience the internet and how the network actually works. A user knows names, websites and service labels. The network works with exact numeric destinations.

If you understand what an IP address is, it becomes much easier to understand why a website may not switch immediately after a hosting migration, why a domain sometimes points to the wrong server, why public and private addresses are discussed separately, or why a website and email service can work independently even though they use the same domain.

That is why IP addresses matter outside purely technical professions too. Website owners, founders, marketers and content managers may not need to manage networks every day, but understanding the role of IP addresses makes many hosting, DNS and service issues much easier to understand.

Related terms

• DNS – domains and hostnames are translated into IP addresses through DNS.
• Hostname – the human-readable service or server name that is then resolved to an IP address.
• Domain – the name a person remembers, while the IP address is the numeric network destination the domain ultimately leads to.
• Nameservers – authoritative nameservers store the DNS records that determine which IP address a domain or hostname should lead to.
• A record – the DNS record that maps a domain name or hostname to an IPv4 address.
• AAAA record – the DNS record that maps a domain name or hostname to an IPv6 address.
• IPv4 – the older and still widely used version of the Internet Protocol addressing system.
• IPv6 – the newer version of the Internet Protocol with a much larger address space.