[`launch`](settings.md#launch) statement (`pdns_server --launch=gpgsql --config`),
all settings related to that backend (and their defaults) are included in the dump.
+# Virtual Hosting
+It may be advantageous to run multiple separate PowerDNS installations on a
+single host, for example to make sure that different customers cannot affect
+each others zones. PowerDNS fully supports running multiple instances on one host.
+
+To generate additional PowerDNS instances, copy the init.d script `pdns` to
+`pdns-name`, where `name` is the name of your virtual configuration. Must not
+contain a - as this will confuse the script.
+
+When you launch PowerDNS via this renamed script, it will seek configuration
+instructions not in `pdns.conf` but in `pdns-name.conf`, allowing for separate
+specification of parameters.
+
+Internally, the init script calls the binary with the
+[`config-name`](settings.md#config-name) option set to `name`, setting in motion
+the loading of separate configuration files.
+
+When you launch a virtual instance of PowerDNS, the pid-file is saved inside
+[`socket-dir`](settings.md#socket-dir) as `pdns-name.pid`.
+
+**Warning**: Be aware however that the init.d `force-stop` will kill all
+PowerDNS instances!
+
+**Warning**: For systems running systemd, virtual hosting is not yet supported.
+
# Internals
## How PowerDNS translates DNS queries into backend queries
A DNS query is not a straightforward lookup. Many DNS queries need to check the
* String
Name of this virtual configuration - will rename the binary image. See
-["Virtual hosting"](virtual.md).
+["Virtual hosting"](running.md#virtual-hosting).
## `control-console`
Debugging switch - don't use.
This path will also contain the pidfile for this instance of PowerDNS called
`pdns.pid` by default. See [`config-name`](#config-name) and
-[Virtual Hosting](virtual.md) how this can differ.
+[Virtual Hosting](running.md#virtual-hosting) how this can differ.
## `strict-rfc-axfrs`
* Boolean
+++ /dev/null
-# Virtual Hosting
-It may be advantageous to run multiple separate PowerDNS installations on a
-single host, for example to make sure that different customers cannot affect
-each others zones. PowerDNS fully supports running multiple instances on one host.
-
-To generate additional PowerDNS instances, copy the init.d script `pdns` to
-`pdns-name`, where `name` is the name of your virtual configuration. Must not
-contain a - as this will confuse the script.
-
-When you launch PowerDNS via this renamed script, it will seek configuration
-instructions not in `pdns.conf` but in `pdns-name.conf`, allowing for separate
-specification of parameters.
-
-Internally, the init script calls the binary with the
-[`config-name`](settings.md#config-name) option set to `name`, setting in motion
-the loading of separate configuration files.
-
-When you launch a virtual instance of PowerDNS, the pid-file is saved inside
-[`socket-dir`](settings.md#socket-dir) as `pdns-name.pid`.
-
-**Warning**: Be aware however that the init.d `force-stop` will kill all
-PowerDNS instances!
-
-**Warning**: For systems running systemd, virtual hosting is not yet supported.
- Added a limit on the simultaneous numbers of TCP connections to accept (**max-tcp-connections**). Defaults to 10.
## Bugs fixed
-- When operating in virtual hosting mode (See [Virtual hosting](authoritative/virtual.md "Virtual hosting")), the additional init.d scripts would not function correctly and interface with other pdns instances.
+- When operating in virtual hosting mode (See [Virtual hosting](authoritative/running.md#virtual-hosting "Virtual hosting")), the additional init.d scripts would not function correctly and interface with other pdns instances.
- PDNS neglected to conserve case on answers. So a query for WwW.PoWeRdNs.CoM would get an answer listing the address of www.powerdns.com. While this did not confuse resolvers, it is better to conserve case. This has semantic consequences for all backends, which the documentation now spells out.
- PostgreSQL backend was case sensitive and returned only answers in case an exact match was found. The Generic PostgreSQL backend is now officially all lower case and zone2sql in PostgreSQL mode enforces this. Documentation has been been updated to reflect the case change. Thanks to Maikel Verheijen of Ladot for spotting this!
- Documentation bug - postgresql create/index statements created a duplicate index. If you've previously copy pasted the commands and not noticed the error, execute **CREATE INDEX rec\_name\_index ON records(name)** to remedy. Thanks to Jeff Miller for reporting this. This also lead to depressingly slow 'ANY' lookups for those of you doing benchmarks.
- Dynamic DNS Update: authoritative/dnsupdate.md
- Using TSIG for AXFR: authoritative/tsig.md
- Various How To's: authoritative/howtos.md
- - Virtual Hosting: authoritative/virtual.md
- Performance Tuning and Monitoring: authoritative/performance.md
- Migrating to PowerDNS: authoritative/migration.md
- Recursion with the Authoritative Server: authoritative/recursion.md