Michał Kępień 9e62c206c6 Allow "order none" in "rrset-order" rules ... named-checkconf treats the following configuration as valid: options { rrset-order { order none; }; }; Yet, the above configuration causes named to crash on startup with: order.c:74: REQUIRE(mode == 0x00000800 || mode == 0x00000400 || mode == 0x00800000) failed, back trace Add DNS_RDATASETATTR_NONE to the list of RRset ordering modes accepted by dns_order_add() to allow "order none" to be used in "rrset-order" rules. This both prevents the aforementioned crashes and addresses the discrepancy between named-checkconf and named. (cherry picked from commit dbcf683c1a)		2020-10-02 08:50:51 +02:00
..
bind9	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
dns	Allow "order none" in "rrset-order" rules	2020-10-02 08:50:51 +02:00
irs	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
isc	Refactor the pausing/unpausing and finishing the nm_thread	2020-10-01 18:09:35 +02:00
isccc	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
isccfg	prep 9.16.7	2020-09-16 22:50:38 +02:00
ns	Add separate prefetch nmhandle to ns_client_t	2020-10-01 18:09:35 +02:00
samples	The dns_message_create() cannot fail, change the return to void	2020-09-30 14:26:26 +02:00
win32/bindevt	update all copyright headers to eliminate the typo	2020-09-14 16:50:58 -07:00
.gitignore	added gitignore, removed cvsignore	2012-03-03 23:10:05 -08:00
Kyuafile	link in lib/isccc/tests/Kyuafile	2018-11-13 07:23:36 +11:00
Makefile.in	remove lib/tests as nothing uses it anymore	2018-03-09 14:12:50 -08:00