DNS Testing Tools in Microsoft Windows 98

Microsoft Windows 98 was built on the consumer-focused MS-DOS/Windows 9x architecture, which lacked the advanced native DNS diagnostics found in the enterprise Windows NT line. While dedicated query tools like nslookup were not included out of the box, Windows 98 provided several built-in networking utilities—most notably Ping, Tracert, and Winipcfg—that allowed users to verify DNS server configurations and test hostname-to-IP address resolution.

Ping (PING.EXE)

The primary method for testing DNS resolution in Windows 98 was the ping command-line utility.

When a user executed ping against a Fully Qualified Domain Name (FQDN) rather than an IP address, Windows 98 automatically queried the configured DNS server to resolve the hostname before sending ICMP echo requests.

  • Successful resolution: If DNS was working, the output showed the resolved IP address in brackets (e.g., Pinging example.com [93.184.216.34] with 32 bytes of data:). Even if ICMP packets were blocked by a firewall, the presence of the IP address confirmed successful DNS resolution.
  • Failed resolution: If DNS failed, the tool returned Bad IP host or Unknown host.

Tracert (TRACERT.EXE)

Similar to Ping, the tracert (Trace Route) command-line utility required hostname resolution prior to mapping the network path.

Running tracert <hostname> forced Windows 98 to query the DNS server for the target's IP address. If the query succeeded, the tool printed the target IP and initiated the hop-by-hop trace. If the DNS query failed, execution stopped immediately with an error indicating the system was unable to resolve the target system name.

Winipcfg (WINIPCFG.EXE)

While winipcfg could not send direct DNS lookup queries, it was the official graphical utility in Windows 98 used to verify DNS configuration parameters. It served as the Windows 9x counterpart to Windows NT's ipconfig.

By opening the Run dialog (Win + R), typing winipcfg, and clicking More Info, users could verify:

  • Whether the DNS servers were actively assigned via DHCP or statically defined.
  • The exact IP addresses of the primary and secondary DNS servers.
  • The host name and DNS suffix search list.

Verifying these settings was an essential first step when troubleshooting DNS resolution failures.

The Absence of Nslookup

The standard tool for querying DNS records, nslookup.exe, was exclusive to the Windows NT family (Windows NT 4.0, Windows 2000) and was not natively bundled with Windows 98.

Users who required advanced DNS record inspection (such as MX, CNAME, or NS lookups) in Windows 98 had to rely on third-party Winsock-compatible tools or utilities from the Windows 98 Resource Kit.