"yum update" killed my DNS zones on VMware Server 1.0.3

girarde · 04-16-2009, 02:20 PM

The subject pretty much describes the syndrome. I took a snapshot of a CENTOS 4.2 server running BIND 9.2.4 chrooted, ran yum update under su, and after restarting I had no DNS configuration, and very shortly thereafter pushed it to my ISP. There was no love.

I don't have more info because we needed to revert to snapshot ASAP.

Why would updating packages cream DNS?

archangel_617b · 04-16-2009, 03:41 PM

Quote:

Originally Posted by girarde

The subject pretty much describes the syndrome. I took a snapshot of a CENTOS 4.2 server running BIND 9.2.4 chrooted, ran yum update under su, and after restarting I had no DNS configuration, and very shortly thereafter pushed it to my ISP. There was no love.

I don't have more info because we needed to revert to snapshot ASAP.

Why would updating packages cream DNS?

Were the zone files themselves gone or what? Any idea? My only guess would be that either a new named.conf or else a new location for named.conf lead your DNS server to look in a new (and incorrect) location for your zone files.

- Arch

girarde · 04-16-2009, 05:00 PM

Quote:

Originally Posted by archangel_617b

Were the zone files themselves gone or what? Any idea? My only guess would be that either a new named.conf or else a new location for named.conf lead your DNS server to look in a new (and incorrect) location for your zone files.

- Arch

Well, I don't know if either of those is the case, because I did not dare spend time checking. I had to revert to snapshot IMMEDIATELY.

I marvel at bind changing the location of the .conf file, but then I marvel that anything else would touch anything relating to it as well.

archangel_617b · 04-17-2009, 10:32 AM

So when you load your VM on a test machine and test the upgrade on it, what happens?

- Arch

girarde · 04-20-2009, 10:22 PM

I may not be able to test that - new assignment.