Head's up: bind/named trouble in upstream Fedora 10

[cpg]

some users have been experiencing some trouble with installs - no name resolution after things come up. maybe no network or DHCP.

we just discovered via access to one of these systems (thanks zetass!) that there is an upstream dependency broken in fedora 10 bind. this is bad. for some reason some users may end up like this:

Code: Select all

# rpm -qa bind\* bind-libs-9.5.1-0.8.b2.fc10.i386 bind-utils-9.5.1-0.8.b2.fc10.i386 bind-9.5.2-1.fc10.i386

notice that bind is one version ahead of the others, somehow!?!?

solution for a broken system is:

• patch /etc/resolv.conf to add nameserver 208.67.220.220 (this gets name resolution back for the system)
• yum update -y bind\*
• hdactl-hup

if you do this, please DO report how it goes, as we will want to roll this across the board and it better be SOLID.

[orbit77]

I installed from F10 DVD two days ago with no problem (in this area at least!):

# rpm -qa bind\*
bind-9.5.1-0.8.b2.fc10.i386
bind-utils-9.5.1-0.8.b2.fc10.i386
bind-libs-9.5.1-0.8.b2.fc10.i386

Just FYI

Cheers,
George

[cpg]

thanks for the FYI. it helps to know it's not everyone hitting it.

we're just sensing a disturbance in the force ... and bind if at the core of every hda ... needs to be reliable ...