How to check fqdn

Content on WhatAnswers is provided "as is" for informational purposes. While we strive for accuracy, we make no guarantees. Content is AI-assisted and should not be used as professional advice.

Last updated: April 4, 2026

Quick Answer: To check a Fully Qualified Domain Name (FQDN), you can use command-line tools like `ping` or `nslookup` (on Windows/Linux/macOS) or `dig` (on Linux/macOS). These tools query DNS servers to resolve a hostname into its IP address, effectively verifying its FQDN.

Key Facts

An FQDN consists of a hostname and a domain name (e.g., 'www.example.com').
The `ping` command sends ICMP echo requests to a host, displaying its FQDN if resolved.
The `nslookup` tool allows you to query DNS servers for specific record types.
The `dig` command provides detailed DNS query responses, including FQDN resolution.
FQDNs are crucial for unambiguous identification of devices on the internet.

Overview

A Fully Qualified Domain Name (FQDN), sometimes referred to as an absolute domain name, is the complete domain name for a specific computer, service, or any other resource on the internet. It uniquely identifies a location on the internet. An FQDN consists of a hostname and a domain name, separated by dots. For example, in www.example.com, www is the hostname, and example.com is the domain name. The highest level is the Top-Level Domain (TLD), such as .com, .org, or .net. Understanding and checking FQDNs is essential for network administrators, developers, and even advanced users to ensure correct network configurations and troubleshoot connectivity issues.

Why is Checking FQDN Important?

Verifying an FQDN is important for several reasons:

Network Troubleshooting: If a device is not accessible, checking its FQDN can help determine if the issue lies with DNS resolution or the device itself.
Security: Ensuring that you are connecting to the correct server (e.g., for online banking or email) prevents man-in-the-middle attacks.
Configuration: When setting up servers, services, or network devices, correct FQDN configuration is vital for them to be discoverable and functional.
Website Hosting: For websites to be accessible globally, their FQDN must be correctly registered and pointed to the hosting server's IP address.

Methods to Check an FQDN

There are several command-line tools available on most operating systems to check an FQDN. These tools interact with the Domain Name System (DNS) to resolve hostnames into IP addresses and vice versa.

Using `ping`

The ping command is a basic network utility that sends ICMP (Internet Control Message Protocol) echo requests to a target host. If the host responds, ping will typically display the hostname it resolved the IP address to, which should be the FQDN.

How to use it:

Open your command prompt (Windows) or terminal (macOS/Linux).
Type ping [hostname_or_ip_address] and press Enter. For example: ping google.com or ping 172.217.160.142.

If google.com resolves to 172.217.160.142, and the response shows something like "Pinging google.com [172.217.160.142]", it confirms that google.com is a valid FQDN resolving to that IP. If you ping an IP address and it returns a hostname, that hostname is its FQDN.

Using `nslookup`

nslookup (Name Server Lookup) is a more powerful tool specifically designed for querying DNS servers. It can retrieve various DNS records, including IP addresses (A records for IPv4, AAAA records for IPv6), mail server information (MX records), and more.

How to use it:

Open your command prompt or terminal.
Type nslookup [hostname_or_ip_address] and press Enter. For example: nslookup www.microsoft.com.

The output will show the DNS server used for the query and then list the IP address(es) associated with the FQDN, and often the FQDN itself if you query an IP address. For example, querying 8.8.8.8 might return dns.google as the hostname.

Using `dig`

dig (Domain Information Groper) is another versatile command-line utility, primarily found on Unix-like systems (Linux, macOS), though it can be installed on Windows. It provides more detailed information about DNS queries than nslookup and is often preferred by network professionals.

How to use it:

Open your terminal.
Type dig [hostname] and press Enter. For example: dig example.com.

The output includes the question section (what you asked for), the answer section (the result), and other details like TTL (Time To Live). If example.com is a valid FQDN, the answer section will show its IP address (A record).

Understanding DNS Resolution

When you type an FQDN into your browser or use a command-line tool, your computer initiates a DNS lookup. This process involves querying DNS servers, starting with a local resolver (often provided by your ISP or configured manually), which then contacts root servers, TLD servers, and authoritative name servers until the IP address associated with the FQDN is found. If any step in this chain fails, the FQDN cannot be resolved.

Common Issues and Troubleshooting

Typographical Errors: Ensure the FQDN is spelled correctly.
DNS Propagation: Changes to DNS records can take time (up to 48 hours) to propagate across the internet.
Firewall Restrictions: Firewalls can block DNS queries (UDP/TCP port 53).
Incorrect DNS Configuration: The FQDN might not be correctly registered or pointed to the right IP address in the DNS records.

By using these tools and understanding the underlying DNS process, you can effectively check and verify FQDNs on your network.