In 15.4, I’ve suffered endless problems with the named package. They are:
- A named.conf gets written that includes “named.conf.include”, but the file doesn’t exist.
- Any existing named.conf.include can get overwritten with an empty file, trashing existing config.
- The include mechanism doesn’t work under some circumstances. named terminates with error 6 NOTCONFIGURED at startup if you have include files.
For the last one, there’s probably more information needed.
Can someone PLEASE fix this? I’m having production servers blown out of the water because named gets updated and everything is messed up.
Thanks.
George
It won’t be fixed unless it’s known about…
Report it as a bug at https://bugzilla.opensuse.org (same login credentials as these forums).
Kieltux
3
- Run always rpmconfigcheck after an update
- Look at the list of changed config files generated by rpmconfigcheck (.rpmnew)
- If you don’t use named.conf.include comment the line
[FONT=monospace]include "/etc/named.conf.include";[/FONT]
out in named.conf and edit the file /etc/sysconfig/named and change
NAMED_INITIALIZE_SCRIPTS="createNamedConfInclude"
to
NAMED_INITIALIZE_SCRIPTS=""
- If you use [FONT=monospace]named.conf.include copy it to /etc.
More Info: https://www.suse.com/support/kb/doc/?id=000020819 [/FONT]
Gets written by whom? Does not exist where? Immediately after installation of bind this file certainly does exist (even in at least two places).
- Any existing named.conf.include can get overwritten with an empty file, trashing existing config.
Gets overwritten when? What you did that caused this file to be overwritten and why do you think that named has anything to do with it?
- The include mechanism doesn’t work under some circumstances
For the last one, there’s probably more information needed.
You mean that for the first two it is crystal clear what is the root cause and how to fix it?
Can someone PLEASE fix this?
Probably if you explain how to reproduce it.