Groups | Search | Server Info | Login | Register
Groups > comp.protocols.dns.bind > #16062
| From | John Thurston <john.thurston@alaska.gov> |
|---|---|
| Newsgroups | comp.protocols.dns.bind |
| Subject | 9.11 -> 9.16 via COPR |
| Date | 2020-08-21 11:34 -0800 |
| Message-ID | <mailman.819.1598038458.942.bind-users@lists.isc.org> (permalink) |
| References | <ef4e77ba-fb0c-6d55-58ba-695f0067d175@alaska.gov> |
We're happily running the BIND 9.11 ESV on CentOS 7 by way of: isc-bind-esv/x86_64 Copr repo for bind-esv owned by isc The roadmap I recall indicates 9.11 will move to "security only" updates at the end of 2020, at which time 9.16 is slated to become the ESV. I figure it is time for me to get a 9.16 instance running and see what will be involved in making it work for us. My questions are two: A) How will the upcoming change in ESV-designation appear to users of the COPR packages? Will there come a time when the repository/package "isc-bind-esv" will just deliver 9.16 rather than 9.11? B) If I have a host currently using "isc-bind-esv/x86_64", and I want it instead to use "isc-bind/x86_64", what's the suggested process? Do I "yum remove", replace the "bind-esv" repository with "bind", and "yum install"? Is it simpler than that? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston@alaska.gov Department of Administration State of Alaska
Back to comp.protocols.dns.bind | Previous | Next | Find similar
9.11 -> 9.16 via COPR John Thurston <john.thurston@alaska.gov> - 2020-08-21 11:34 -0800
csiph-web