Created on
10-04-2024
12:47 AM
Edited on
07-29-2025
08:59 AM
By
Stephen_G
| Description | This article describes why FortiProxy sends AAAA DNS queries. In some environments, IPv6 is not in use, so the DNS query for the AAAA record is an unexpected result and causes an HTTP error code 504. |
| Scope | FortiProxy. |
| Solution |
FortiProxy will send AAAA DNS queries to the DNS server when IPv6 or ISDB IPv6 is configured in policies.
config firewall policy edit <policy ID> or set internet-service6-name <ISDB name> next end
If the IPv6 address is in a policy, FortiProxy may send both A and AAAA DNS queries to the DNS server. In some cases, if the AAAA record query response arrives before the A record and the response is Server failure, AAAA or unresolvable, FortiProxy will return the error HTTP 504 to the user.
The WAD debug logs confirm that IPV6 DNS queries are being sent.
i.e from WAD debugs:
CONNECT www.golem.de:443 HTTP/1.1 Host: www.golem.de:443 Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36 Edg/137.0.0.0 [I][p:1929][s:84133835][r:88811933] wad_http_str_canonicalize :2200 enc=0 path=/ len=1 changes=0
In this case, the IPv6 address must be removed from the policies |
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.