## pdns\_control commands
### `bind-add-zone <domain> <filename>`
-Add zone \<domain\> from \<filename\> to PDNS's bind backend. Zone will be loaded at first request.
+Add zone <domain> from <filename> to PDNS's bind backend. Zone will be loaded at first request.
### `bind-domain-status <domain> [domain]`
Output status of domain or domains. Can be one of 'seen in named.conf, not parsed', 'parsed successfully at \<time;\>' or 'error parsing at line ... at \<time\>'.
Reloads a zone from disk NOW, reporting back results.
### `rediscover`
-Reread the bind configuration file (`named.conf`). If parsing fails, the old configuration remains in force and pdns\_control reports the error. Any newly discovered domains are read, discarded domains are removed from memory.
+Reread the bind configuration file (`named.conf`). If parsing fails, the old configuration remains in force and `pdns_control` reports the error. Any newly discovered domains are read, discarded domains are removed from memory.
**Note**: Except that with 2.9.3, they are not removed from memory.
All zones with a changed timestamp are reloaded at the next incoming query for them.
## Performance
-The BindBackend does not benefit from the packet cache as it is fast enough on its own. Furthermore, on most systems, there will be no benefit in using multiple CPUs for the packetcache, so a noticeable speedup can be attained by specifying `distributor-threads=1` in `pdns.conf`.
+The BindBackend does not benefit from the packet cache as it is fast enough on its own. Furthermore, on most systems, there will be no benefit in using multiple CPUs for the packetcache, so a noticeable speedup can be attained by specifying [`distributor-threads`](settings.md#distributor-threads)`=1` in `pdns.conf`.
## Master/slave configuration