1 files changed, 20 insertions, 17 deletions
diff --git a/share/man/man5/resolv.conf.5 b/share/man/man5/resolv.conf.5
index 1c96c9f12de..6430760c31b 100644
--- a/share/man/man5/resolv.conf.5
+++ b/share/man/man5/resolv.conf.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: resolv.conf.5,v 1.45 2014/08/23 07:25:54 jmc Exp $
+.\"	$OpenBSD: resolv.conf.5,v 1.46 2014/11/05 15:12:23 jmc Exp $
 .\"	$NetBSD: resolv.conf.5,v 1.7 1996/03/06 18:22:16 scottr Exp $
 .\"
 .\" Copyright (c) 1986, 1991 The Regents of the University of California.
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)resolver.5	5.12 (Berkeley) 5/10/91
 .\"
-.Dd $Mdocdate: August 23 2014 $
+.Dd $Mdocdate: November 5 2014 $
 .Dt RESOLV.CONF 5
 .Os
 .Sh NAME
@@ -266,21 +266,24 @@ non-EDNS0 DNS servers,
 so the option must be used only when all the servers listed in
 .Cm nameserver
 lines are able to handle the extension.
-.Pp
-To verify whether a server supports EDNS,
-query it using the
-.Xr dig 1
-query option
-.Li +edns=0 :
-the reply indicates compliance (EDNS version 0)
-and whether a UDP packet larger than 512 bytes can be used.
-Note that EDNS0 can cause the server to send packets
-large enough to require fragmentation.
-Other factors such as packet filters may impede these,
-particularly if there is a reduced MTU,
-as is often the case with
-.Xr pppoe 4
-or with tunnels.
+By default on
+.Ox
+this option does nothing.
+.\" .Pp
+.\" To verify whether a server supports EDNS,
+.\" query it using the
+.\" .Xr dig 1
+.\" query option
+.\" .Li +edns=0 :
+.\" the reply indicates compliance (EDNS version 0)
+.\" and whether a UDP packet larger than 512 bytes can be used.
+.\" Note that EDNS0 can cause the server to send packets
+.\" large enough to require fragmentation.
+.\" Other factors such as packet filters may impede these,
+.\" particularly if there is a reduced MTU,
+.\" as is often the case with
+.\" .Xr pppoe 4
+.\" or with tunnels.
 .It Cm inet6
 Enables support for IPv6-only applications, by setting RES_USE_INET6 in
 _res.options (see