User Tools

Site Tools


pfsense:dns:troubleshooting:notice_sendto_failed_permission_denied

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
pfsense:dns:troubleshooting:notice_sendto_failed_permission_denied [2021/01/06 14:07] – created peterpfsense:dns:troubleshooting:notice_sendto_failed_permission_denied [2021/01/06 14:22] (current) peter
Line 11: Line 11:
 {{:pfsense:unbound:troubleshooting:pssense_dns_resolver_notice_sendto_failed_permission_denied.png?800|}} {{:pfsense:unbound:troubleshooting:pssense_dns_resolver_notice_sendto_failed_permission_denied.png?800|}}
  
-The resolver settings are not dynamically checking/applying upstream ipv4/6 connectivity but assuming both active.+----
  
-Enable or disable whether ip6 queries are answered or issued.  Default is yes.+===== Cause & Fix =====
  
-If disabled, queries are not answered on IPv6, and queries are not sent on IPv6 to the internet name-servers.+==== IPv6 could be disabled on the WAN port ====
  
-With this option you can disable the ipv6 transport for sending DNS traffic, it does not impact the contents of the DNS traffic, which may have ip4 and ip6 addresses in it.+<WRAP info> 
 +**NOTE:**  The resolver settings are not dynamically checking/applying upstream ipv4/6 connectivity but assuming both are active.
  
 +Simply ignore for these messages for now, or allow IPv6 on the WAN.
 +
 +</WRAP>
 +
 +----
 +
 +==== Suricata may be blocking these addresses ====
 +
 +Usually due to **ET DNS Query to a *.pw domain - Likely Hostile**.
 +
 +----
 +
 +==== Unbound may have crashed ====
 +
 +In the past Unbound could crash with a buffer overflow.  
 +
 +But this should have been fixed.
 +
 +----
  
  
pfsense/dns/troubleshooting/notice_sendto_failed_permission_denied.1609942079.txt.gz · Last modified: 2021/01/06 14:07 by peter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki