Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
zebwani
New Contributor

Accept: DNS error

many accept : DNS error

 

4 REPLIES 4
Dovlat
New Contributor

Our FortiGate firewall has the same alert, Any explanation, hardly find anything reference

RachelGomez123
Contributor

Tips to Fix the “DNS Server Not Responding” Error in Windows and macOS (10 Methods)
Switch to a Different Browser. 
Start Your Computer in Safe Mode. 
Temporarily Disable Your Antivirus Software and Firewall. 
Disable Secondary Connections. 
Disable the Windows Peer-to-Peer Feature.

Restart Your Router.

 

Regards,

Rachel Gomez

aahmadzada
Staff
Staff

This is an expected behavior where the firewall logs any invalid DNS traffic.

Invalid DNS traffic would be UDP packets on port 53 that are not DNS traffic, packets which are oversized, bad checksum etc or this happens also if the DNS query is not successful returns any other status than NOERROR.

 

 

Ahmad
ede_pfau
Esteemed Contributor III

I see you specified the DNS root servers as DNS1, DNS2. I would change that to your ISP's DNS, and a reliable public DNS as secondary DNS (like 9.9.9.9 or 8.8.8.8). Chances are high that the nearest DNS is at your ISP and will respond quickest.


Ede

"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
Labels
Top Kudoed Authors