Skip to main content
rain
Staff
Staff
September 2, 2026

Technical Tip: FortiGate DNS does not show status/MS state and not DNS resolution

  • September 2, 2026
  • 2 replies
  • 119 views

Description

This article describes how to solve the issue when the FortiGate does not show any status at the 'ms' (milliseconds) level, and there is also no DNS resolution.

Scope

FortiGate system.

Solution

There are scenarios where the FortiGate does not show any DNS status or 'ms', and the resolution does not work at all. This could be an issue with the daemon at the kernel level that does not initialize correctly.

 

In order to check if the daemon/process is fine, do the following:

Check if, after changing the IPs over the DNS and also the protocols, the status is not shown and the screen is white all the time

 

Go to Network -> DNS and check if there is no status.


1ab55707.png

 

Expected status/MS even in an 'unreachable' state means the DNS daemon is up and running:


8919a01c.png

 

Also, if checking the process when searching for 'DNS', the process is not there, which means that the process/daemon is not initialized, and because of that, the DNS will never work.


af651a6c.png

 

In order to solve this issue, a reboot of the FortiGate will be needed in order to initialize the process. A KILL or restart of the process will not work because the process never started in the first place. After doing the reboot, the DNS will start fine and will show the status/MS, and also the resolution will work again.

    2 replies

    New Member
    September 3, 2026

    Thanks for sharing this troubleshooting guide. The explanation about the DNS daemon not initializing correctly is especially helpful. Checking for the missing DNS process and confirming whether the status/MS values are completely absent is a good way to distinguish this from a normal DNS connectivity issue. It’s also useful to know that a FortiGate reboot may be required when the daemon never started, rather than simply restarting or killing the process.

    New Member
    September 3, 2026

    Helpful troubleshooting tip. If the DNS daemon isn’t initialized, a reboot being the required fix is a useful detail to know. The expected status/MS indicators also make it much easier to confirm whether the DNS service is running properly.

    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!