- 09 Jul, 2018 1 commit
-
-
Daniel Salzman authored
-
- 06 Jul, 2018 4 commits
-
-
Libor Peltan authored
-
Libor Peltan authored
-
Libor Peltan authored
-
Libor Peltan authored
-
- 02 Jul, 2018 1 commit
-
-
Mark Karpilovskij authored
-
- 28 Jun, 2018 4 commits
-
-
Daniel Salzman authored
-
Libor Peltan authored
-
Libor Peltan authored
-
Daniel Salzman authored
-
- 31 May, 2018 1 commit
-
-
Daniel Salzman authored
-
- 21 May, 2018 2 commits
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- 17 May, 2018 3 commits
-
-
Daniel Salzman authored
-
Libor Peltan authored
-
Daniel Salzman authored
This reverts commit e3f52c20.
-
- 15 May, 2018 5 commits
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Libor Peltan authored
-
Wolfgang Jung authored
-
- 04 May, 2018 1 commit
-
-
Daniel Salzman authored
-
- 30 Apr, 2018 1 commit
-
-
Daniel Salzman authored
-
- 23 Apr, 2018 2 commits
-
-
Daniel Salzman authored
-
Mark Karpilovskij authored
-
- 11 Apr, 2018 1 commit
-
-
Daniel Salzman authored
-
- 09 Apr, 2018 3 commits
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- 06 Apr, 2018 1 commit
-
-
Mark Karpilovskij authored
-
- 04 Apr, 2018 1 commit
-
-
Daniel Salzman authored
-
- 27 Mar, 2018 2 commits
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- 20 Mar, 2018 4 commits
-
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
Daniel Salzman authored
-
- 18 Mar, 2018 1 commit
-
-
Daniel Salzman authored
-
- 16 Mar, 2018 2 commits
-
-
Mark Karpilovskij authored
-
Libor Peltan authored
this bug bahaves like this: if you configure: dnssec-signing: on zonefile-load: difference it will, upon changing zonefile, make inconsistencies in journal leading in broken IXFR the reason is that by calling set_new_soa over existing SOA in changeset (probably because of zone_update_from_differences) it updates the changeset's soa_from to incorrect value
-