The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Hostname identifies one device or service, a domain name identifies a registered namespace, and an FQDN (fully qualified domain name) combines the two into a complete DNS address. Server name is not a precise DNS category: depending on the product or administrator, it may mean the machine’s hostname, a display name, or a configuration value such as a virtual-host name.
For a game server, for example, arena7 can be the host’s local name, example.net can be the registered domain, and arena7.example.net is the full name used to locate that host in DNS.
As an Amazon Associate I earn from qualifying purchases.
The four terms at a glance
| Term | What it identifies | Example | How it is assigned | Formal DNS status |
|---|---|---|---|---|
| Hostname | One device or service on a network | mail, arena7 |
Usually chosen by an administrator on the local network | Common operational term; standards use the spelling inconsistently |
| Domain name | A registered namespace containing hosts and other records | example.com |
Registered and globally unique | Part of the DNS hierarchy |
| FQDN | One exact host name inside a domain, written completely | mail.example.com. |
Derived by combining labels; the final dot denotes the DNS root | Absolute DNS name |
| Server name | Whatever a product or administrator calls a server | Varies by software | Set during installation or in configuration | Informal; not a distinct DNS record type or namespace |
The practical test is scope. A hostname points to one host or service, a domain groups names under a registered suffix, and an FQDN leaves no part of the DNS path implicit. “Server name” requires context because different software uses it differently.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What a hostname is
A hostname is a label assigned to a particular computer, virtual machine, container, or network service. On a small local network, names such as desktop, nas, voice, or arena7 make machines recognizable without requiring users to remember an address.
#1 Best Overall
Hostnames in a game-server setup
Suppose a studio runs three dedicated game instances. It might assign the machines the local hostnames eu-match-01, eu-match-02, and us-match-01. Those labels distinguish individual systems. They do not, by themselves, prove that the names are registered on the public Internet or that players outside the local network can resolve them.
A hostname can also describe a service rather than a physical box. An administrator may call a machine node3 while using match as the service label that players should use. The exact relationship depends on the DNS and application configuration.
Who chooses a hostname?
On a private network, an administrator can generally choose a useful, unique label according to local policy. Operating-system installers often ask for a computer name, and hosting platforms may generate one automatically. Local uniqueness matters: two devices using the same hostname can make identification and name resolution confusing even when their IP addresses differ.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA local hostname is not automatically globally unique. Another organization can independently use the same label, such as server1, on its own network.
Is “hostname” a formally defined DNS term?
It is widely used, but the standards history is less tidy than everyday documentation suggests. RFC 9499 notes that “host name” and “hostname” are common expressions without a single definition in RFC 1034, RFC 1035, RFC 1123, or RFC 2181. In operational writing, the safest interpretation is still “the label that identifies a host,” while checking the product’s own terminology when precision matters.
What a domain name is
A domain name is a name in the hierarchical Domain Name System (DNS). A registered domain, such as example.com, provides a namespace under which an organization can create host and service names. The domain is broader than any one machine: it can contain www.example.com, mail.example.com, arena7.example.com, and many other labels.
Registration makes a domain globally unique
Unlike a private hostname, a public domain is registered through the domain-name system so that the name is unique in the global DNS namespace. Registration gives the organization control over that domain’s DNS data; it does not automatically create a machine or guarantee that every possible subdomain exists.
For a game community, the domain might be example.net. The domain itself is the shared address space. Individual game servers normally receive additional labels beneath it, such as survival.example.net or arena7.example.net.
Domain name versus website
A domain is not synonymous with a website. The same domain can name web, mail, voice, administration, and game services. A browser may use one host label, while a game client uses another; both can belong to the same registered domain.
What an FQDN is
An FQDN (fully qualified domain name) specifies a host’s complete position in DNS. It combines the host label with every required domain label. Thus, arena7.example.net identifies the arena7 host within example.net.
The trailing dot matters
In DNS notation, the fully absolute form is arena7.example.net. The final dot represents the root of the DNS hierarchy. It tells software that the name is complete and must not have a local search suffix appended.
Recommended Free Tools
Many user interfaces hide that final dot and display arena7.example.net. The name can still be an FQDN in ordinary documentation; the explicit trailing-dot form is useful when explaining DNS behavior or writing zone-file data.
Absolute and relative names
RFC 1034 distinguishes an absolute name, which is complete and ends at the root, from a relative name, which local software completes using a configured domain or search list. For example, arena7 might be expanded to arena7.example.net. on one network but to a different suffix on another.
This is why a short hostname can work on an office or home network while the same text fails for an Internet user. The resolver may know a local suffix that an outside client does not.
Why “server name” causes confusion
“Server name” is an informal expression, not a separate DNS object. In one control panel it may mean the operating system’s hostname. In another, it may be a friendly label shown in a server list. Web-server software can also use a server-name setting to select a virtual host, while a game-management panel may use the same words for the name players see.
Three common meanings
- Machine name: the computer’s hostname, such as
node3. - DNS name: the address players enter, such as
arena7.example.net. - Application label: a display or configuration value, such as “North America Ranked,” that may not be registered in DNS at all.
These values can be identical, but they do not have to be. A server may have the operating-system hostname node3, the DNS name arena7.example.net, and the in-game display name “Arena 7.” Asking which field a setup guide means prevents many connection errors.
Rank #3
- Used Book in Good Condition
How Microsoft terminology fits
Microsoft documentation commonly treats the computer name as the host name. In a name such as server1.widgets.microsoft.com, it describes server1 as the leftmost, relative distinguished name. That usage explains why Windows administration screens may call a value the computer name while networking documentation calls the corresponding label a hostname.
How the pieces fit together
Think of a DNS name as a sequence of labels separated by dots. In arena7.example.net.:
arena7is the host or service label.exampleis the registered domain label.netis the top-level domain.- The final dot is the root, making the written name absolute.
The hostname and domain are therefore not competing names for the same thing. They occupy different levels of the hierarchy. An FQDN is the complete combination; a “server name” may refer to any one of these values depending on the software.
Free tools Windows power users keep installed
One-click scans. No signup required.
Hostname, domain and FQDN: practical comparisons
| Question | Hostname | Domain name | FQDN | Server name |
|---|---|---|---|---|
| Does it identify one machine? | Usually yes | No; it provides a namespace | Yes, when the final host label is unique | Only if the product uses it for the machine name |
| Must it be globally unique? | No, not on a private network | Yes when publicly registered | It is unique within the DNS namespace that defines it | Not necessarily |
| Can it be used by a game client? | Only when the client can resolve that local name | Usually as a suffix, not the complete host address | Yes, this is the unambiguous DNS form | Only if the application maps it to a reachable address |
| Who controls it? | Local administrator or hosting platform | Domain registrant and DNS administrators | Those controlling the relevant hostname and domain | The software or system administrator |
| Is it a formal DNS category? | Common term with standards ambiguity | Yes, a DNS namespace concept | Yes, an absolute fully specified name | No |
How to choose the right name for a game server
Step 1: Decide what players should enter
Start with the name visible to players, not the machine’s internal label. If the server should be reachable as arena7.example.net, document that exact address. If players connect through a private network, a short hostname may be sufficient, but state the required network or search suffix.
Step 2: Give the machine a distinct hostname
Choose a short, descriptive hostname such as eu-match-01. Keep it unique among your systems and make the naming pattern predictable. A hostname that describes location, role, and sequence is easier to identify during maintenance than a random generated string.
Step 3: Keep the public name separate when roles differ
If the same machine hosts several game instances, do not assume its machine hostname should be the player-facing name. Use separate service labels where your DNS and application configuration support them. This lets you move a game instance to another machine without changing the address players know.
Step 4: Write down the FQDN explicitly
Configuration documents should record the complete name, including its domain. When discussing DNS behavior or editing data that distinguishes absolute from relative names, include the trailing dot: arena7.example.net.. In player instructions, the conventional no-dot form is usually easier to read.
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 glitchesStep 5: Confirm what each control-panel field means
Before saving a setting called “server name,” check its help text or documentation. Determine whether it changes the operating-system hostname, a DNS address, a virtual-host match, or only a display label. Entering an FQDN into a field that expects a short hostname can produce invalid or confusing configuration.
Rank #4
Verifying names on common systems
Use the operating system to inspect the local hostname, then use a DNS lookup utility to test the name players will use. The exact output varies by operating-system version and resolver configuration.
Windows
- Open Settings → System → About and note the Device name. This is the computer’s local name.
- Open a terminal and run
hostnameto print the current hostname. - Run
nslookup arena7.example.netand check whether the configured resolver returns the expected address or an explicit “non-existent domain” response.
Linux
- Run
hostnamectlto view the static and transient hostname values where supported. - Run
hostname --fqdnto see the FQDN that the local system believes applies. If it returns only a short name or an unexpected suffix, inspect the local hostname and resolver configuration. - Run
dig arena7.example.netorgetent hosts arena7.example.netto test name resolution from that machine.
These checks answer different questions. The first group reports local identity; the lookup commands test whether a name can be translated through DNS. A successful local hostname check does not prove that an external player can resolve the public FQDN.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.DNS naming rules and length limits
DNS names are made from labels. Each label is limited to 63 octets, and a complete DNS name is limited to 255 octets. The limits are measured in octets rather than simply counting visible characters, which matters for names containing non-ASCII representations.
Use labels that tools accept consistently
For maximum compatibility across operating systems, hosting panels, and game clients, use a simple pattern of letters, digits, and hyphens, and avoid spaces in host labels. Keep the registered domain and the host label visually distinct so administrators can tell which part is being changed.
Do not confuse a long display name with a DNS label
A game’s public title can contain spaces, punctuation, and promotional wording because it is an application-level display string. The DNS host label should follow DNS and client-validation rules instead. Store the friendly title in the game configuration and the resolvable address in the network configuration.
Common failure modes and fixes
A short hostname works locally but not for remote players
Cause: the short name depends on a local search suffix or private resolver.
Fix: provide the complete FQDN, such as arena7.example.net, and test it from a network outside the local environment. If the service is intentionally private, tell users which network or resolver they must use.
The “server name” field rejects an FQDN
Cause: the field expects a machine hostname or an application label rather than a DNS address.
Fix: inspect the field’s documented format. Put the short hostname in the system-name field, the FQDN in the address or DNS field, and the player-facing title in the display-name field.
Two machines appear under the same name
Cause: duplicate local hostnames or copied system images.
Fix: assign each machine a unique hostname, restart or reload the relevant naming service, and update any configuration that refers to the old value.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A name resolves inside the data center but not on the Internet
Cause: internal and external DNS views differ, or the name exists only in a private zone.
Fix: test from both environments and document whether the address is intended to be private. Do not assume that a successful lookup from the server proves public reachability.
A trailing dot produces an error in a game client
Cause: some application input validators accept the common host form but reject explicit root notation.
Fix: use the client’s accepted form, usually arena7.example.net, while retaining arena7.example.net. in technical DNS documentation when an absolute name must be shown.
A decision checklist
- Are you naming one computer or service? Use a hostname.
- Are you referring to the registered namespace shared by many services? Use the domain name.
- Do you need the complete, unambiguous DNS address? Use the FQDN.
- Does a form say “server name”? Find out whether it expects a hostname, FQDN, or display label.
- Will users connect from outside the local network? Prefer the externally resolvable FQDN and test it from an external resolver.
- Are you writing DNS or infrastructure documentation? Show the trailing dot when distinguishing an absolute name from a relative one.
- Could the name exceed DNS limits? Keep every label at 63 octets or fewer and the complete name at 255 octets or fewer.
The simplest mental model
Imagine a building directory. The domain is the building’s registered address space, the hostname is a room or service label inside it, and the FQDN is the full directory path that identifies the room without relying on local assumptions. “Server name” is whatever a particular sign, form, or application chooses to call one of those labels.
For a game server, keep three values separate in your documentation: the machine hostname used by administrators, the FQDN players resolve, and the friendly in-game name they see. Treating those as distinct prevents the most common setup mistakes while leaving you free to move services between machines later.
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.
