- Mar 20, 2017
-
-
instead of hard-changing msgID in packet wire, which breaks msgID for the response, we just set the original msgID when computing the tsig hash to check against
-
- Mar 10, 2017
-
-
- Mar 07, 2017
-
-
- Mar 02, 2017
-
-
- Feb 27, 2017
-
-
- Feb 21, 2017
-
-
- Feb 03, 2017
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- Feb 02, 2017
-
-
Daniel Salzman authored
-
- Feb 01, 2017
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- Jan 29, 2017
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- Jan 27, 2017
-
-
Daniel Salzman authored
-
- Jan 25, 2017
-
-
Filip Široký authored
-
Daniel Salzman authored
-
- Jan 24, 2017
-
-
Daniel Salzman authored
-
-
- Jan 17, 2017
-
-
-
-
Daniel Salzman authored
-
- Jan 16, 2017
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- Jan 15, 2017
-
-
Jan Včelák authored
-
- Jan 14, 2017
-
-
Jan Včelák authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- Jan 13, 2017
-
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- Jan 11, 2017
-
-
Libor Peltan authored
-
- Jan 07, 2017
-
-
Jan Včelák authored
BIND limits the number of sent notify messages to one master server. This is controlled by serial-query-rate (older versions) or notify-rate and startup-notify-rate (since 9.9.7-S1 and 9.11.1). This increases the limit so that BIND sends all messages we expect. And also disables notify delaying.
-
- Jan 04, 2017
-
-
Libor Peltan authored
-
Libor Peltan authored
-
- Dec 29, 2016
-
-
Daniel Salzman authored
-
-