A fully qualified domain name (FQDN) is the complete, publicly resolvable DNS name of a host, such as mail.example.com. SMTP uses these names to identify servers and find destinations. If your mail server introduces itself as localhost, an internal-only name, or an unresolvable public hostname, receiving systems may reject messages or delivery may fail.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Fixing the hostname is necessary but not sufficient. Reliable delivery also requires working MX and address records, coherent reverse DNS, and correctly aligned SPF, DKIM, and DMARC authentication.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat “fully qualified domain name” means
DNS names form a hierarchy. In mail.example.com, mail identifies the host, example is the domain, and com is the top-level domain. Together, those labels identify one host in the global DNS namespace. The name is “fully qualified” because it states the complete path rather than relying on a local search suffix or nickname.
An FQDN must be resolvable in the DNS context where it is used. A local alias such as mailserver, localhost, or smtp.internal may work inside a private network, but it does not identify a publicly reachable host for Internet SMTP.
#1 Best Overall
| Name | What it is | Suitable for public SMTP identity? |
|---|---|---|
mail.example.com |
Complete host name under a registered domain | Yes, when its DNS records resolve correctly |
example.com |
A domain name; it can also be a mail destination if configured with MX or address records | Potentially, depending on the server role and records |
mailserver |
Unqualified local name | No |
localhost |
Loopback name for the local machine | No |
smtp.internal |
Private or non-public namespace | No for Internet-facing SMTP |
203.0.113.25 |
IPv4 address literal | Only as a limited SMTP exception when a host has no usable name |
RFC 5321 is explicit: “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.” Those requirements apply to names used in the SMTP conversation, not merely to labels shown in your mail application.
Where SMTP uses an FQDN
Finding the recipient’s mail server
When an SMTP client has a recipient domain, it must perform a DNS lookup. The delivery process first looks for an MX record for that domain. If the DNS answer contains a CNAME, the CNAME target is followed, and the resulting name must ultimately resolve to an MX or an address record. If the domain does not exist, the lookup is an error.
The MX record identifies which host accepts mail for a domain. The target host then needs an address record, normally A for IPv4, AAAA for IPv6, or both. An MX record that points to a name with no usable address leaves the sending server without a destination it can connect to.
Presenting the sending server with EHLO or HELO
At the start of an SMTP session, the client identifies itself with EHLO (or HELO). RFC 5321 requires that this identity be a primary host name that resolves to an address record. If the host has no name, an address literal is permitted as an exception.
Rank #2
- Linux
- Linux DNS
That makes localhost, an internal suffix, or a made-up public name a problem even when the mail-transfer application is running normally. The receiving server can test the name independently of your operating system and may reject the connection, assign a poor trust score, or record a protocol error when the name does not resolve.
Why an invalid FQDN can cause bounces
“Missing FQDN” is not one universal SMTP bounce code. The response depends on what failed and on the receiving server’s policy. A message can fail because the destination domain has no usable DNS, because your server’s EHLO name cannot be resolved, because forward and reverse identity conflict, or because authentication policy rejects the message. Read the complete SMTP diagnostic text rather than searching only for the word “bounce.”
Recommended Free Tools
Destination DNS failures
If the recipient domain does not exist, has no MX and no usable fallback address, or has an MX target that cannot be resolved, your server cannot locate a delivery host. The message may be deferred while DNS is retried or returned to the sender after the retry period.
Sending-host identity failures
A receiver can check the name presented in EHLO. A name that has no public A or AAAA record, resolves only inside your network, or resolves to an unrelated address can trigger a policy rejection. Some receivers accept the connection but treat the mismatch as a reason to score the message as suspicious.
Reverse-DNS and forward-DNS mismatch
Internet-facing mail servers commonly need a PTR record for their sending IP. The IP provider controls that reverse-DNS record. A coherent setup has the PTR point to mail.example.com, while the A or AAAA record for mail.example.com points back to the same sending address. The standards do not impose one universal bounce response for a mismatch, but receivers frequently include it in anti-abuse policy.
Authentication or alignment failures
FQDN resolution does not authenticate a message. SPF uses DNS to associate an envelope-From domain with authorized sending infrastructure. DKIM signs selected message data with a domain name. DMARC evaluates alignment between authenticated identifiers and the visible From domain, then tells receivers whether to deliver, quarantine, or reject failures and where to send reports.
RFC 9989 explains that SPF can validate both the HELO/EHLO identity and the MAIL identity, while DMARC relies on SPF validation of the MAIL FROM identity. A server can therefore have a valid hostname and still fail SPF, DKIM, or DMARC checks.
| Observed symptom | Likely area to inspect | First check |
|---|---|---|
| “Name or service not known” or an inability to connect to the recipient | Recipient DNS, MX target, or address record | Resolve the recipient domain’s MX and each MX host from outside your network |
| Rejection immediately after EHLO | Unresolvable or disallowed EHLO name | Resolve the exact name your server sends and compare it with the public host record |
| “Reverse DNS,” “PTR,” or “hostname” appears in the response | Reverse-DNS control or forward/reverse mismatch | Perform a reverse lookup of the sending IP and a forward lookup of the returned name |
| SPF, DKIM, or DMARC failure | Authentication records or identifier alignment | Inspect the envelope sender, DKIM signing domain, visible From domain, and their DNS policies |
| Temporary deferrals followed by a final bounce | Repeated DNS, connection, policy, or reputation failure | Read the final diagnostic and test the named host or policy condition directly |
How to give a mail server a correct public identity
- Control a registered domain. Use a domain such as
example.comfor which you can edit authoritative DNS. - Choose one public mail hostname. A conventional choice is
mail.example.com. Use the same name consistently in server configuration, documentation, and reverse DNS. - Publish address records. Create an A record for the server’s IPv4 address and an AAAA record when the server is intentionally reachable over IPv6. Do not publish an address that does not route to the mail host.
- Configure the SMTP identity. Set the MTA’s primary hostname and its EHLO/HELO value to the resolvable mail hostname. Restart or reload the service according to that software’s procedure, then confirm the value in an outbound session log.
- Configure the recipient domain’s MX. If the server receives mail for
example.com, publish an MX record for that domain pointing to the mail host. The MX target itself must resolve to an address record. - Request reverse DNS from the IP provider. Ask the hosting company or ISP that controls the sending address to set its PTR record to the same mail hostname. DNS control in your domain does not normally grant control over the IP’s PTR record.
- Add authentication records. Publish SPF for authorized senders, enable DKIM signing, and publish a DMARC policy after checking that the authenticated domains align with the visible From domain.
This sequence separates prerequisites from policy. A DMARC record cannot make an unresolvable EHLO name valid, and a PTR record cannot create an MX record for a recipient domain.
DNS records involved in mail identity
| Record or setting | Role | What a correct relationship looks like |
|---|---|---|
A / AAAA for mail.example.com |
Maps the mail hostname to reachable IPv4 and/or IPv6 addresses | The address is the one used by the SMTP server and is reachable from the Internet |
MX for example.com |
Names the host that accepts mail for the domain | The MX target is a resolvable host with an A or AAAA record |
| PTR for the sending IP | Provides the reverse name of the address | The PTR points to the mail hostname, whose forward record points back to that address |
| SPF TXT | Lists infrastructure authorized for an envelope-From domain | The sending IP or service is covered by the published policy |
| DKIM TXT and signer | Publishes the public key for a cryptographic signature | The selector record exists and the message is signed with the intended domain |
| DMARC TXT | Defines handling and reporting for authentication failures | The policy is published at the visible From domain and its alignment mode matches your design |
How to test the setup from outside your network
Testing from the same LAN can hide split-DNS or firewall problems. Use a system that is not using your internal resolver, or an external DNS checking service, and query each dependency separately.
- Resolve the mail hostname’s address records, for example with
dig A mail.example.comanddig AAAA mail.example.com. Confirm that the returned addresses are current and reachable. - Resolve the recipient domain’s mail route with
dig MX example.com. For every MX target returned, query its A and AAAA records. - Check reverse DNS with
dig -x 203.0.113.25, replacing the example address with your real sending IP. Then resolve the PTR name forward and compare the result. - Inspect your MTA’s delivery log to verify that the EHLO/HELO value is the intended FQDN, not a package default such as
localhost. - Send a controlled test to a mailbox you administer and preserve the complete rejection or delivery headers. Look for the receiver’s exact SMTP response, the envelope sender, authentication results, and the host name used in the transaction.
A successful local lookup proves only that one resolver answered. The receiving server may use different DNS servers, see a different IPv6 route, or apply policy that your test host does not. Treat the receiver’s diagnostic text as the authoritative clue for the failed transaction.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Self-hosted mail versus a managed SMTP service
The standards define the identity and lookup requirements, but operational responsibility differs by deployment model. Provider-specific limits, geographic coverage, support quality, and pricing vary and must be checked for the service you choose.
| Consideration | Self-hosted server | Managed SMTP service |
|---|---|---|
| DNS and reverse-DNS control | You configure forward records; PTR depends on your IP provider | The service usually supplies sending hosts; you still configure domain records and may not control provider PTR names |
| SPF, DKIM, and DMARC | You publish records and operate signing and policy enforcement | The provider supplies record values or setup instructions; you remain responsible for publishing and aligning them |
| Bounce diagnostics | You read MTA logs, queue state, and remote SMTP responses | The service may expose event logs and categorized bounces, with detail depending on the product |
| Deliverability operations | You handle IP reputation, blocklists, throttling, updates, and abuse complaints | The provider operates shared or dedicated infrastructure and its own abuse processes |
| Sending limits and geography | Determined by your network, IP reputation, and recipient policies | Determined by the provider’s account, region, and acceptable-use rules |
| Operational cost | You bear server, DNS, monitoring, maintenance, and incident-response work | You trade that work for a service charge and dependency on the provider’s availability and policies |
Choose self-hosting only when you can maintain DNS, reverse DNS, authentication, monitoring, and abuse handling. A managed service reduces infrastructure work, but it does not remove the need to publish an accurate sending domain and keep authentication aligned.
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
Common configuration mistakes and targeted fixes
The server says “localhost” in EHLO
Set the system’s canonical hostname and the MTA’s outgoing identity to the public mail FQDN. Confirm that the name has a public address record, then send another test and inspect the transcript to ensure the old value is gone.
The hostname resolves internally but not publicly
Publish the record in the authoritative public DNS zone rather than only in an internal resolver. Test from an external network. If you intentionally use split DNS, make sure the public answer still contains the address needed by Internet peers.
The MX record points to an alias with no address
Follow the MX target and any CNAME in the chain. Ensure the final target has an A or AAAA record. An MX entry that stops at an unresolved name cannot accept mail.
PTR points to a different host
Ask the address provider to change the PTR, then make the corresponding forward A or AAAA record resolve to the same sending IP. Allow DNS caches to expire before judging the result.
Authentication passes for one domain but DMARC fails
Compare the domain in the envelope MAIL FROM, the DKIM signing domain, and the visible From header. SPF or DKIM can pass while DMARC fails if the authenticated domain is not aligned with the visible From domain. Correct the sender configuration or publish policy that matches your intended alignment.
What an FQDN fixes—and what it does not
A correct FQDN gives SMTP peers a stable, resolvable identity and lets DNS locate mail destinations. It does not guarantee inbox placement, prove that a message is legitimate, or override a recipient’s filtering policy. SPF, DKIM, and DMARC address authentication and policy; reverse DNS supports coherent host identity; network reputation, message content, volume, and recipient rules remain separate factors.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →For a bounce investigation, verify the chain in this order: the recipient domain exists, its MX route resolves, your EHLO name resolves, forward and reverse DNS agree, and authentication records cover the actual sender. The first failed dependency usually explains the receiver’s diagnostic response.
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.
