| Description | This article describes how to troubleshoot and resolve an issue where traffic using the hostname as a destination fails while the same traffic using a Fully Qualified Domain Name FQDN works as expected. The lab example in this article uses FortiGate as a DHCP server and a DNS database server for demonstration purposes. However, the network concept is not vendor-specific. |
| Scope | FortiGate - FortiOS. |
| Solution |
The following screenshot shows that the ECHO requests are receiving a reply when the FQDN is the target while failing to resolve the hostname when the destination is hostname:
To fix this issue, DNS-Suffix needs to be added to this client machine either manually, by modifying the IPV4 advanced settings, or automatically, by obtaining it from the DHCP server via DHCP option 15.
When the FortiGate is the DHCP server, the option is available in the CLI via the following configuration:
The result is that the source machine now adds the DNS-Suffix to the DNS query, which results in FortiGate as a DNS server being able to lookup the destination and provide the response with the matching IP. The following is the output of 'diagnose debug application dnsproxy -1' for illustration purposes:
[worker 0] udp_receive_request()-3199: vd=0, vrf=0, intf=7, len=33, alen=16, 10.56.1.2:52266=>10.56.1.1
The ping command receives a reply when the target is the hostname:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.