Delete .IP macros from man pages

Author: Jeroen Koekkoek

nsd-checkzone.8.in

@@ -37,14 +37,14 @@ command write does.
 Create an IXFR from the differences between the old zone file and the
 new zone file. The argument to the \-i option is the old zone file,
 the other zonefile argument passed is the new zonefile.
-.IP
+
 The difference is computed between the two zonefiles by keeping one
 version of the zone in memory, and another version in a temporary
 file. The temporary file is located at the zonefile directory. This is
 also where the result is written, to a file with the zonefile name,
 ending with '.ixfr'. This is also where NSD reads it when IXFRs are
 configured for the zone.
-.IP
+
 The other existing ixfr files are renamed to become older IXFR contents
 for the zone, if any such files exist.  If the output file already exists
 with the correct contents, no new file is created. The contents of the

nsd.conf.5.in

@@ -147,15 +147,15 @@ NSD will bind to the listed ip\-address. Can be given multiple times
 to bind multiple ip\-addresses. Optionally, a port number can be given.
 If none are given NSD listens to the wildcard interface. Same as command-line option
 .BR \-a.
-.IP
+
 To limit which NSD server(s) listen on the given interface, specify one or
 more servers separated by whitespace after <ip>[@port]. Ranges can be used as
 a shorthand to specify multiple consecutive servers. By default every server
 will listen.
-.IP
+
 If an interface name is used instead of ip4 or ip6, the list of IP addresses
 associated with that interface is picked up and used at server start.
-.IP
+
 For servers with multiple IP addresses that can be used to send traffic
 to the internet, list them one by one, or the source address of replies
 could be wrong.  This is because if the udp socket associates a source
@@ -302,7 +302,7 @@ Increase it to allow more zone transfer sockets, like to 256.
 To save memory, this can be lowered, set it lower together with some other
 settings to have reduced memory footprint for NSD. xfrd\-tcp\-max: 32
 and xfrd\-tcp\-pipeline: 128 and rrl\-size: 1000
-.IP
+
 This reduces memory footprint, other memory usage is caused mainly by
 the server\-count setting, the number of server processes, and the
 tcp\-count setting, which keeps buffers per server process, and by the
@@ -398,14 +398,14 @@ Default is 0. 1 gives more information about incoming notifies and
 zone transfers. 2 lists soft warnings that are encountered. 3 prints
 more information. Same as command-line option
 .BR \-V .
-.IP
+
 Verbosity 0 will print warnings and errors, and other events that are
 important to keep NSD running.
-.IP
+
 Verbosity 1 prints additionally messages of interest.  Successful notifies,
 successful incoming zone transfer (the zone is updated), failed incoming
 zone transfers or the inability to process zone updates.
-.IP
+
 Verbosity 2 prints additionally soft errors, like connection resets over TCP.
 And notify refusal, and axfr request refusals.
 .TP
@@ -536,7 +536,7 @@ service port number.  The port number (853) is configured with tls\-port.
 To turn it on, create an interface: option line in config with @port
 appended to the IP-address.  This creates the extra socket on which the
 DNS over TLS service is provided.
-.IP
+
 The file is the private key for the TLS session. The public certificate is
 in the tls-service-pem file. Default is "", turned off. Requires a
 restart (a reload is not enough) if changed, because the private key is
@@ -568,7 +568,7 @@ If you want to use mutual TLS authentication in Transfer over TLS (XoT) connecti
 this is where the primary server enables a dedicated port for this purpose. Certificates in
 .BR tls-cert-bundle
 are used for verifying the authenticity of a client or a secondary server.
-.IP
+
 Client (secondary) must enable
 .BR tls-auth ,
 configure
@@ -621,10 +621,10 @@ NSD will bind to the listed addresses to service control requests
 Use 0.0.0.0 and ::0 to service the wildcard interface.  If none are given
 NSD listens to the localhost 127.0.0.1 and ::1 interfaces for control,
 if control is enabled with control\-enable.
-.IP
+
 If an interface name is used instead of ip4 or ip6, the list of IP addresses
 associated with that interface is picked up and used at server start.
-.IP
+
 With an absolute path, a unix local named pipe is used for control.  The
 file is created with user and group that is configured and access bits
 are set to allow members of the group access.  Further access can be
@@ -802,24 +802,24 @@ each zone.
 The file containing the zone information. If this attribute is present
 it is used to read and write the zone contents. If the attribute is
 absent it prevents writing out of the zone.
-.IP
+
 The string is processed so that one string can be used (in a pattern)
 for a lot of different zones.  If the label or character does not exist the
 percent-character is replaced with a period for output (i.e. for the
 third character in a two letter domain name).
-.IP
+
 .B %s\fR is replaced with the zone name.
-.IP
+
 .B %1\fR is replaced with the first character of the zone name.
-.IP
+
 .B %2\fR is replaced with the second character of the zone name.
-.IP
+
 .B %3\fR is replaced with the third character of the zone name.
-.IP
+
 .B %z\fR is replaced with the toplevel domain name of the zone.
-.IP
+
 .B %y\fR is replaced with the next label under the toplevel domain.
-.IP
+
 .B %x\fR is replaced with the next-next label under the toplevel domain.
 .TP
 .B allow\-query:\fR <ip\-spec> <key\-name | NOKEY | BLOCKED>
@@ -1061,7 +1061,7 @@ property, or if a group property is missing or invalid, the pattern specified
 by the \fBcatalog\-member\-pattern\fR option is used. Group properties are valid
 if there is only a single value matching the name of a for member zones valid
 pattern.
-.IP
+
 A zone with the option set to \fIproducer\fR, can be used to produce a
 catalog zone.  Member zones for catalog producer zones can be added with
 "\fInsd\-control addzone <zone> <pattern>\fR", where <pattern> has a
@@ -1071,17 +1071,17 @@ Catalog producer zones must be primary zones and may not have a
 \fBrequest\-xfr\fR option. Catalog producer zones will \fInot\fR read content
 from zone files, but will reconstruct the zone on startup from the member zone
 entries in @zonelistfile@, specified with the \fBzonelistfile\fR option.
-.IP
+
 The status of both catalog consumer and producer zones can be verified with
 \fInsd\-control zonestatus\fR. It will show the number of member zones and, if
 the catalog zone is invalid, the reason for it to be invalid is shown.
 \fInsd\-control zonestatus\fR will also show the entry of a catalog member zone
 in the catalog (consumer or producer) zone as \fBcatalog-member-id:\fR.
-.IP
+
 A catalog zone can either be catalog consumer zone or a catalog producer zone
 but not both. Likewise, catalog member zones can be either a member of catalog
 consumer zone or a catalog producer zone but not both.
-.IP
+
 Catalog zones contain a list of zones that are served. Use \fBallow\-query:
 0.0.0.0/0 BLOCKED\fR and \fBallow\-query: ::0/0 BLOCKED\fR in a catalog zone 
 zone or pattern clause to prevent revealing the catalog. Also consider using