Debian reconsiders init-system diversity
Debian reconsiders init-system diversity
Posted Nov 22, 2019 10:55 UTC (Fri) by Wol (subscriber, #4433)In reply to: Debian reconsiders init-system diversity by smurf
Parent article: Debian reconsiders init-system diversity
It required the network service to be running when it shut down, else it would get stuck in an infinite loop. If your system happened to shut down networking before bind ... if it was in a remote co-lo you were SOL.
Oh and I think this took *years*, *if ever* to get fixed in the official repo.
Cheers,
Wol
Posted Nov 24, 2019 20:59 UTC (Sun)
by flussence (guest, #85566)
[Link] (3 responses)
Posted Nov 27, 2019 17:01 UTC (Wed)
by anselm (subscriber, #2796)
[Link]
BIND 9 actually borders on the usable. In addition, while there are loads of purported “BIND replacements” they often implement only that part of the functionality of a DNS server that their authors like or agree with. If one desires a DNS server which actually does everything that the RFCs say a DNS server should do, the number of feasible substitutes for BIND is suddenly not all that large anymore.
Which is not to say that there aren't BIND replacements that are useful in many contexts (I'm a happy user of PowerDNS and dnsmasq, for example) – it's just that the “BIND replacements” tend to come with their own sets of issues. Hence, caveat emptor.
Posted Nov 28, 2019 11:13 UTC (Thu)
by jezuch (subscriber, #52988)
[Link] (1 responses)
Posted Nov 29, 2019 4:04 UTC (Fri)
by flussence (guest, #85566)
[Link]
Debian reconsiders init-system diversity
Debian reconsiders init-system diversity
Debian reconsiders init-system diversity
Debian reconsiders init-system diversity