A fully qualified domain name (FQDN) is the complete, publicly resolvable DNS name of a host, such as mail.example.com. Internet SMTP expects real FQDNs—not shortcuts such as localhost, an internal-only name, or an unregistered alias—when servers identify themselves or a delivery destination. If that name cannot be resolved, or its forward and reverse DNS do not make sense together, a receiving server may defer or reject mail.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
An FQDN is necessary but not sufficient for delivery. You also need working MX and address records, a coherent SMTP greeting, reverse DNS, and correctly aligned SPF, DKIM, and DMARC. The exact bounce response depends on which check failed and on the receiver’s policy.
As an Amazon Associate I earn from qualifying purchases.
What “fully qualified domain name” means
DNS names form a hierarchy. In mail.example.com, com is the top-level domain, example is the registered domain, and mail identifies a host or service beneath it. The complete name is the FQDN. It is different from a short local name such as mail, an operating-system alias, or localhost.
RFC 5321 treats a non-qualified name as a local alias and states: “Local aliases MUST NOT appear in any SMTP transaction.” It also says: “Only resolvable, fully-qualified domain names (FQDNs) are permitted when domain names are used in SMTP.” In practical terms, the name you place in an SMTP command or greeting must exist in DNS and resolve from the public Internet when the transaction is Internet-facing.
#1 Best Overall
FQDN, hostname and domain are not interchangeable
- Registered domain:
example.com. This is the parent namespace used for mail addresses and policies. - Host FQDN:
mail.example.com. This normally identifies the machine that sends or receives mail. - Local hostname:
mailorserver1. It can work inside a private network but is not a valid public SMTP identity. - Address literal: an SMTP client can use an IP address in brackets in the limited case where the host has no name. A stable public FQDN is preferable for normal mail operations.
Having a domain suffix in a string does not make it an FQDN. mail.example.internal is still unsuitable for public SMTP if that namespace is not published and resolvable on the Internet.
Where SMTP uses the FQDN
Finding the recipient’s mail server
Once an SMTP client identifies the domain to which it will deliver a message, RFC 5321 requires a DNS lookup. Delivery first attempts to find an MX record for that domain. If the DNS answer is a CNAME, the target is processed, and the resulting name must resolve to an MX record or an address record. A nonexistent domain is an error.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →For a message addressed to [email protected], the sending server therefore looks up the DNS information for example.com, selects an eligible MX host, and then resolves that host to an address before opening a connection. A missing MX, a target that has no A or AAAA address, or a name that does not exist can stop delivery before authentication is even considered.
Presenting the sending server in EHLO or HELO
At the start of an SMTP session, the client identifies itself with EHLO (or the older HELO). RFC 5321 requires that name to be the client’s primary host name and that it resolve to an address record. An address literal is the exception for a host with no name.
Rank #2
- Linux
- Linux DNS
Using localhost, a workstation name, an internal suffix, or a public-looking name with no DNS record can trigger policy checks. The application may be running normally, yet the receiving server can reject the connection because the identity in the greeting cannot be verified.
Matching forward and reverse identity
Your mail host normally needs a public A or AAAA record, while the IP provider controls the reverse-DNS (PTR) record. Ask that provider to set the PTR to the same mail hostname, then ensure the hostname resolves forward to the sending IP. This forward-confirmed relationship is not a substitute for authentication, but mismatches are a common reason for reputation and policy failures.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why an email bounces when the FQDN is wrong
“Missing FQDN” is not one universal SMTP bounce code. A receiver may reject during connection, return a temporary deferral, or accept the message and later generate a delivery-status notification. Read the diagnostic text and enhanced status code; they identify whether the failure was DNS, routing, policy, authentication, or something else.
Common failure paths
- Unresolvable EHLO name: The greeting names a host that has no public A or AAAA record, so the receiver cannot validate the client identity.
- Broken recipient DNS: The destination domain does not exist, has no usable MX, or its MX target cannot be resolved to an address.
- Forward/reverse mismatch: The sending IP’s PTR points to one name while that name points elsewhere, or the PTR is absent when a receiver requires it.
- Internal-only naming: A server advertises
server.local,mail.lan, or another private suffix that outside DNS resolvers cannot see. - Authentication policy failure: SPF, DKIM, or DMARC fails after the basic connection succeeds. The receiver’s policy may quarantine or reject the message even though the FQDN resolves.
Do not infer the cause from the word “bounce” alone. A permanent DNS error, a temporary inability to reach an MX host, and a DMARC rejection can all appear as bounced mail but require different fixes.
How SPF, DKIM and DMARC relate to an FQDN
Authentication reinforces DNS identity; it does not repair a nonexistent hostname or MX record. SPF uses DNS policy to associate an envelope-From domain with authorized sending infrastructure. SPF can also validate the domain used in the HELO or EHLO identity. DKIM signs a message with a domain name that receivers retrieve through DNS. DMARC evaluates alignment between authenticated identifiers and the visible From domain, then tells receivers whether to deliver, quarantine, or reject failures while producing reports.
| Mechanism | What DNS supplies | What a failure means |
|---|---|---|
| SPF | An authorization policy for the envelope-From domain and, where checked, the HELO/EHLO identity | The sending IP is not authorized for that identity, or the policy cannot be evaluated |
| DKIM | A public key under the signing domain | The signature is missing, invalid, or the key cannot be retrieved |
| DMARC | A policy and reporting record for the visible From domain | Aligned SPF and DKIM authentication is absent; receiver action follows the published policy |
A server can pass SPF, DKIM, and DMARC and still fail because its EHLO name is invalid or the recipient’s MX is broken. Conversely, perfect forward and reverse DNS does not authorize a sender that is absent from SPF or fails DMARC alignment.
Fix an SMTP hostname and reverse-DNS problem step by step
- Control a registered domain. Use a domain you can administer, such as
example.com. You need access to its authoritative DNS zone. - Choose one public mail hostname. Create a stable name such as
mail.example.com. Do not uselocalhost, a bare short hostname, or a private suffix. - Publish the host’s address records. Add an A record for IPv4 and, if you will send over IPv6, an AAAA record. Each address must route to the mail server. Check from an external resolver with commands such as
dig +short A mail.example.comanddig +short AAAA mail.example.com. - Publish the recipient domain’s MX record. If your server receives mail for
example.com, create an MX record whose target is the chosen FQDN, then verify that the target itself resolves to an address. Do not point an MX record at a name with no A or AAAA record. - Set the SMTP identity. Configure the mail transfer agent’s primary hostname and its EHLO/HELO value to
mail.example.com. Restart or reload the service as required by that software, then inspect a live SMTP session to confirm the greeting. - Set reverse DNS with the IP provider. Request a PTR record for the sending IP that returns
mail.example.com. After the change, query the PTR and then query the A/AAAA record for the returned name. Keep the names coherent rather than creating a PTR that points to an unrelated host. - Publish SPF for every legitimate sender. Authorize the actual outbound IP addresses or approved sending services in the SPF record for the envelope-From domain. Keep a single SPF policy at that domain; multiple independent SPF records cause evaluation errors.
- Enable DKIM signing. Generate a key pair in the mail system, publish its public key at the selector name in DNS, and sign outgoing messages with the domain you intend to align with the visible From address.
- Publish DMARC deliberately. Start with a monitoring policy while reviewing reports and correcting alignment. Move to quarantine or reject only after legitimate sources pass and the policy reflects your operational choice.
- Test outside your own network. Query A, AAAA, MX, PTR, SPF, DKIM, and DMARC records from an independent resolver or a second network. Internal DNS can hide a missing public record or return split-horizon answers that receivers never see.
- Read the receiver’s diagnostic. Capture the complete SMTP response, including the enhanced status code and text. A message that says the host is unknown points to DNS or naming; a policy or authentication message requires SPF, DKIM, DMARC, or reputation work.
Verification checks and expected results
Use these checks to isolate the layer that is failing:
dig MX example.comshould return the destination domain’s MX host when the domain accepts mail directly.dig A mail.example.comanddig AAAA mail.example.comshould return the public addresses used by the server.dig -x 203.0.113.10should return the PTR name assigned by the address provider; substitute your real sending IP.- An SMTP transcript should show
EHLO mail.example.com(or the server’s equivalent configured FQDN), not a local alias. - SPF, DKIM, and DMARC lookups should return one authoritative policy each, and message headers should show which mechanisms passed, failed, or were skipped.
DNS changes can be cached according to their TTL. Test from more than one resolver before concluding that a change failed, and avoid changing several unrelated records at once; otherwise the next bounce will be harder to diagnose.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Self-hosted mail server or managed SMTP service?
The standards-based requirements are the same, but operational responsibility differs. Compare the options on the dimensions below before moving production mail.
| Decision point | Self-hosted server | Managed SMTP service |
|---|---|---|
| DNS and reverse DNS | You must publish the host records and obtain PTR control from your IP provider | The provider usually supplies sending hostnames; confirm which records and PTR settings you control |
| SPF, DKIM and DMARC | You configure policies, keys, rotation and alignment | The service may generate records and sign messages; you still publish and maintain them in your domain |
| Bounce diagnostics | You inspect logs, SMTP replies and queue state | Dashboards and webhooks may expose categorized bounces; verify retention and detail |
| Geographic deliverability | Depends on your network, IP reputation and routing | Depends on the provider’s pools, regions and traffic controls |
| Sending limits | Set by your network, receiving policies and reputation | Set by the service’s account, throughput and compliance rules |
| Operational cost | Infrastructure, monitoring, security and abuse handling are yours | Fees are recurring and vary by volume, support and features |
A managed service can reduce server maintenance, but it does not eliminate the need to publish correct domain records or align the visible From domain. Self-hosting gives more control over identity and logs, while making reverse DNS, reputation and incident response your responsibility.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTroubleshooting by symptom
“Host unknown” or “name does not resolve”
Check the exact name in the SMTP greeting and the recipient address domain. Query it from outside your network. Correct the A, AAAA, MX, or CNAME chain, wait for the relevant TTL, and test again. If the name is intentionally private, replace it with a public FQDN for Internet mail.
“Reverse DNS failed” or “PTR missing”
Only the IP address holder can normally change PTR. Contact that provider, request the mail hostname, and make sure a forward lookup of that hostname returns the same sending IP. A PTR pointing to a generic provider name does not establish the identity you configured in EHLO.
Best Value
- Standard size: 6 pink server note pads, Each Book Comes with 50 bound order slips - that's 300 ticket sheets total! Check Pads Size 6.75 x 3.5 inch.
- Convenient Work: These guest check books for servers have a tear-free dotted line that is easy to rip off. You can give as a customer copy or keep for record keeping. We've provided extra rows on the back for additional note taking.Perfect For Restaurants, Lounges, Hotels, Cafes, And Waiters To Use.
- Record Important Information: These server note pads can record important information.Each ticket has a unique serial number printed at the top, dates, order details, number of guests, order amount, table numbers etc. They are lightweight, small and can fit most aprons. They can be used on-demand and can help decrease errors in orders, while improving work efficiency.
- High Quality: Sturdy, Not Drop Powder, It's Thick, You Can Write On The Back And Front Easily.Their whole page printing has clear handwriting and a reasonable layout. On the customer retention part of each guest check, "THANK YOU" on the back to make customers feel appreciated.
- Contact Us: We're confident that the quality of the server note pads will go beyond your expectation. If you experience an issue, feel free to contact us, we'll appreciate it to learn from your experience, and we'll make it better
“Relay denied” or an authentication-policy rejection
Confirm that the server is authorized to relay for the sender, then inspect SPF authorization, DKIM verification, and DMARC alignment. Do not respond by merely changing the EHLO string: authentication policy and relay permissions are separate controls.
Temporary deferrals that later become bounces
Record the first response, not only the final notification. A receiver may defer while an MX host is unreachable, while DNS is propagating, or while reputation checks run. Persistent deferrals after records are correct usually require reviewing queue retries, network reachability, rate limits, and the receiver’s stated policy.
Free tools Windows power users keep installed
One-click scans. No signup required.
The practical takeaway
Give every Internet-facing mail server one stable, publicly resolvable FQDN; publish matching forward and reverse DNS; use that name in EHLO/HELO; and configure MX, SPF, DKIM, and DMARC coherently. When mail bounces, use the receiving server’s exact diagnostic to determine which layer failed instead of treating “no FQDN” as a single universal error.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
