Bug #3533
closed
bind package restores outdated config.xml
0%
Description
Apparently under some circumstances the bind package re-creates config.xml from old values which made me drop using it so I won't be able to reproduce more stuff.
Over 3 days I've been observing my config being destroyed all over again until I noticed that when I changed some BIND setting old interface/routing/... settings where restored from where-ever-several-days-ago.
Updated by Chris Buechler about 11 years ago
That's what would happen if the package corrupted the XML, it would restore from the last good backup. Is it logging in the system log that it's doing that? Do you have a specific set of steps you can take to replicate?
Updated by Andreas Pflug about 11 years ago
All I can see from the config history is that after my last sane change "(system): save result config file for zone on xml" is logged, with a lot of outdated stuff restored; nothing in the syslog AFAIR.
I had zone sync enabled for 2 downstream servers.
Updated by Renato Botelho about 11 years ago
You can also check if a /conf/config.xml.bad file is present when it happens, this file would be the broken XML that caused the issue.
Updated by Andreas Pflug about 11 years ago
I've never seen a config.xml.bad.
Besides, the erroneously restored config is way older than the last known good, many generations actually.
Updated by Chris Buechler over 10 years ago
- Category changed from DNS Server to BIND
- Status changed from New to Feedback
- Affected Version deleted (
2.1)
haven't heard of anyone else seeing this.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Closed