.. warning::
However, please note that your backend can get queries in
- aNy CAsE! If your database is case sensitive, like most are (with the
+ aNy CAsE! If your database is case-sensitive, like most are (with the
notable exception of MySQL), you must make sure that you do find answers
which differ only in case.
* Do not busy loop if we get lots of notifies.
* Improve error reporting with garbage in the 'master' field of the database
* Do not exit on exception resolving addresses to notify
- * Auth ringbuffer summaries were case sensitive & accounted delegations incorrectly
+ * Auth ringbuffer summaries were case-sensitive & accounted delegations incorrectly
* plug mysql_thread_init memory leak
* Ensure we increase the number of queued queries before decreasing it
wasted memory and also led to the continued non-existence of hosts
that since had come into existence.
- The Generic SQL backends did not lowercase the names of records,
- which led to new records not being found by case sensitive databases
+ which led to new records not being found by case-sensitive databases
(notably PostgreSQL). Found by Volker Goetz.
- NS queries for zones for which we did not carry authority, but only
had delegation information, had their NS records in the wrong
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
+- 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 updated to reflect the case change.
prefix.
- zone2sql now accepts a ^^zone-name parameter
- BindBackend maturing - 9500 zones parsed in 3.5 seconds. No longer
- case sensitive.
+ case-sensitive.
Performance enhancements
^^^^^^^^^^^^^^^^^^^^^^^^
If the address starts with an ``h``, it is assumed to be a DoH endpoint, and *PORT* is ignored.
If qname and qtype are both `-` and tcp is used, multiple lines are read from stdin, where each line contains a qname and a type.
If the address is ``stdin``, a DNS packet is read from stdin instead of from the network, and *PORT* is ignored.
-All input is literal and case sensitive.
+All input is literal and case-sensitive.
Queries need option `recurse` to expect a resource record reply if the query target is not known to be the authoritative server for that record.
Options