NS Problem Cause by Yum

[Raymond]

Hi all,
im having problems with named ever since yum update it. i was having problems with apache too but i found out how to roll it back to 1.3.x. the problem i have here is similar to the tread on

http://www.directadmin.com/forum/showthread.php?threadid=10523&highlight=bind

but for mine case it more special in the sense that, even if i manually update /var/named/chroot/etc/named.conf all the domains/subdomains which i created still dont resolve. is there a way to roll back/fix/recompile this bind issue which is cause by yum? im running FC3.

i know this is not a DA issue thanks a lot in advance if anyone could help.

 

[nobaloney]

My guess is you have an RPM installed for caching-nameserver; updating it will overwrite your named.conf file.

The bad news is that the named.conf file is heavily changed by DA.

The good news is that the update should have created named.conf.rpm-save somewhere.

So look for that file and copy it to somewhere safe (perhaps /root).

And remove caching-nameserver from your configuration:

rpm -e caching-nameserver

Then copy that named.conf.rpm-save file over your named.conf file.

And restart BIND.

Jeff

 

[Raymond]

hey Jeff,

thanks a lot for lending a helping hand. bad news it still wont work after i tried what u advice. any other alternatives? im having a guess on here, is it because my rndc key screwed up? i notice two rncd.key in /etc and /var/named/chroot/etc both are off different values so which is the right one?

many thanks in advance.

 

[nobaloney]

We've never had to change the rndc key file.

I'm going to refuse to guess further; I hope you understand.

You need to check your /etc/named.conf file and see to it that it has all your domains listed in it with references to the proper zone file in the /var/named directory.

If it doesn't, then you need to rebuild it or ask someone else to rebuild it for you.

Jeff

 

[gbjbaanb]

I have a quick Q about the named.conf, I'm not sure if mine was trashed or not...

My named.conf looks like this:

// Default named.conf generated by install of bind-9.2.4-2
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
};
include "/etc/rndc.key";


followed by zone entries that reference files in /var/named.

Does this look correct? I really ask because of the comment at the top...

thanks.

 

[nobaloney]

Yes. When yum updates caching-nameserver it deletes all those includes.

Which are still there but you have to fix the file as above.

Jeff