From: W.C.A. Wijngaards <wouter@nlnetlabs.nl>
Date: Tue, 25 Feb 2020 08:58:32 +0000 (+0100)
Subject: Documentation for prefer-ip4, Issue #165.
X-Git-Tag: release-1.11.0~130
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=de35486fb7df1aa00dfb0d3de457f7c2bc1d2489;p=thirdparty%2Funbound.git

Documentation for prefer-ip4, Issue #165.
---

diff --git a/doc/example.conf.in b/doc/example.conf.in
index 4ce9348c2..30a767d62 100644
--- a/doc/example.conf.in
+++ b/doc/example.conf.in
@@ -70,6 +70,9 @@ server:
 	# Set this to yes to prefer ipv6 upstream servers over ipv4.
 	# prefer-ip6: no
 
+	# Prefer ipv4 upstream servers, even if ipv6 is available.
+	# prefer-ip4: no
+
 	# number of ports to allocate per thread, determines the size of the
 	# port range that can be open simultaneously.  About double the
 	# num-queries-per-thread, or, use as many as the OS will allow you.
diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in
index aef2e977f..541a93688 100644
--- a/doc/unbound.conf.5.in
+++ b/doc/unbound.conf.5.in
@@ -381,6 +381,13 @@ IPv6 to the internet nameservers.  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.
 .TP
+.B prefer\-ip4: \fI<yes or no>
+If enabled, prefer IPv4 transport for sending DNS queries to internet
+nameservers. Default is no.  Useful if the IPv6 netblock the server has,
+the entire /64 of that is not owned by one operator and the reputation of
+the netblock /64 is an issue, using IPv4 then uses the IPv4 filters that
+the upstream servers have.
+.TP
 .B prefer\-ip6: \fI<yes or no>
 If enabled, prefer IPv6 transport for sending DNS queries to internet
 nameservers. Default is no.