RHN Bind Update Brings Down RHEL Named

alexs writes "Red Hat's response to update bind through RHN, patching the DNS hole, made a fatal error which will revert all name servers to caching only servers. This meant that anyone running their own DNS service promptly lost all of their DNS records for which they were acting as primary or secondary name servers. Expect quite a few services provided by servers running RHEL to, errr, die until their system administrators can restore their named.conf. Instead of installing etc/named.conf to etc/named.rpmnew, Red Hat moved the current etc/named.conf to etc/named.conf.rpmsave and replaced etc/named.conf with the default caching only configuration. The fix is easy enough, but this is a schoolboy error which I am surprised Red Hat made. Unfortunately we were hit and our servers went down overnight while RHN dropped its bomb and I am frankly surprised there has not been more of an uproar about this."

Comments

But, you plan on making one!

[C_Kode]

I am frankly surprised there has not been more of an uproar about this. ...but you plan on making one! OOH-RA!

Re:A schoolboy error?

[geekymachoman]

IMHO, rhel should have tested this. If they announce offical new version of some app, and it turns out to brake stuff, then that's theirs fault. Maybe admins should stop being lazy, and start installing 'network' services which are crucial server components, by hand, from source, which gives them more flexibility and control then rpm -i.. No ? Ok then, chrooting ? I chroot my bind's, so, if I update, the rpm package can only mess up files like /etc/named.conf which I don't use, since all of config files are in /chroot/named/ and redhat isnt aware of that. Binary file has a switch to start from chroot... you edit /etc/sysconfig/bind or something like that, and do /etc/init.d/named start - Thats it. If you can easyli chroot some service (like named), then do it. You can only gain something from it.

Does anyone test anything any more?

[Master of Transhuman]

I don't think testing is done by anyone - commercial company or OSS - on anything any more.

I updated to Firefox 3 from the openSUSE repositories, and have been using it for the last week. I had to uninstall it yesterday when the frustration got too great.

Firefox 3 has a serious right-click menu bug, wherein any right click you do may select any item on the right click context menu without bringing up the menu. Hard to believe this wouldn't have been caught in testing.

Also Firefox 3 locks up or crashes on about every third Web site, including sites I have no trouble with in Firefox 2. Can you say "LOUSY JavaScript support"?

For all the hype over Firefox 3, I knew there would be issues when I saw how compressed the time frame was from beta to release candidate to final release.

They simply didn't test the thing. I mean, some Windows users are complaining they can't open Gmail! Gmail! Probably the most heavily used Webmail service - and Mozilla couldn't test Firefox 3 with it?

Pathetic.

Since I had upgraded Firefox 2 to 3, I read where somebody suggested wiping the old profile and reinstalling. I did that - no change.

Firefox 3 is not read for prime time. I will not reinstall it until they get to Firefox 3.1 at least.

Never install a point 0 release of anything. The entire industry simply is incapable of producing a solid product on a zero point release.