We've got several CentOS 3.x systems running DNS that we keep updated automatically via YUM.
Recently two of those systems (not all of them) when updating themselves to the latest versions of BIND, automatically replaced /etc/named.conf with a new one and saved the old one as /etc/named.conf.rpmsave.
Which of course broke DNS for those servers.
All servers got updated, but only two of them did the rewrite.
Any ideas as to why it might have happed, or how to make sure it doesn't happen again?
Hopefully nothing so simplistic as "exclude bind from auto updates" though if that's the only answer, we'll take it.
Thanks.
Jeff
remove pkg caching-nameserver then restore named.conf.rpmsave, restart bind
Jeff Lasman wrote:
We've got several CentOS 3.x systems running DNS that we keep updated automatically via YUM.
Recently two of those systems (not all of them) when updating themselves to the latest versions of BIND, automatically replaced /etc/named.conf with a new one and saved the old one as /etc/named.conf.rpmsave.
Which of course broke DNS for those servers.
All servers got updated, but only two of them did the rewrite.
Any ideas as to why it might have happed, or how to make sure it doesn't happen again?
Hopefully nothing so simplistic as "exclude bind from auto updates" though if that's the only answer, we'll take it.
Thanks.
Jeff
On Wed, 2005-06-22 at 19:31 -0700, Jeff Lasman wrote:
We've got several CentOS 3.x systems running DNS that we keep updated automatically via YUM.
Recently two of those systems (not all of them) when updating themselves to the latest versions of BIND, automatically replaced /etc/named.conf with a new one and saved the old one as /etc/named.conf.rpmsave.
Which of course broke DNS for those servers.
All servers got updated, but only two of them did the rewrite.
Any ideas as to why it might have happed, or how to make sure it doesn't happen again?
Hopefully nothing so simplistic as "exclude bind from auto updates" though if that's the only answer, we'll take it.
Thanks.
Jeff
It is probably not bind that is causing your issues, but caching- nameserver.
RH says you should not have caching-nameserver installed on a machine that is also doing domain control.
So save your named.conf also maybe the hints file (usually /var/named/named.ca) ... then remove caching-nameserver ... then restore your config files and you should not have this issue in the future. See these links:
probably because they have caching-nameserver installed.
On Wed, 22 Jun 2005, Jeff Lasman wrote:
We've got several CentOS 3.x systems running DNS that we keep updated automatically via YUM.
Recently two of those systems (not all of them) when updating themselves to the latest versions of BIND, automatically replaced /etc/named.conf with a new one and saved the old one as /etc/named.conf.rpmsave.
Which of course broke DNS for those servers.
All servers got updated, but only two of them did the rewrite.
Any ideas as to why it might have happed, or how to make sure it doesn't happen again?
Hopefully nothing so simplistic as "exclude bind from auto updates" though if that's the only answer, we'll take it.
Thanks.
Jeff
-
Jeff Lasman -
Johnny Hughes -
Maciej Żenczykowski -
Tom