BIND 9.7.1-P2 caching name server crash

Bind suffered from a crash on one of our caching servers, a core dumb for named was generated. We are running BIND 9.7.1-P2, on rhel 5.5, kernel 2.6.18-194.el5. The only useful log lines found at the crash time are from "general.log", following are the lines: 27-Aug-2010 16:43:04.901 query.c:178

Re: cant update 'cz'

On Aug 28 2010, clem...@dwf.com wrote: I am getting the message: cz DNSKEY: please check the 'trusted-keys' for 'cz' in named.conf. And in the past this has meant that something needed to be updated. However, when I pull 'anchors.xml' and run anchors2keys < anchors.xml > trusted.keys the

cant update 'cz'

I am getting the message: cz DNSKEY: please check the 'trusted-keys' for 'cz' in named.conf. And in the past this has meant that something needed to be updated. However, when I pull 'anchors.xml' and run anchors2keys < anchors.xml > trusted.keys there is no entry for 'cz'. What should I be

Re: migrate to a different IP

Steve.. Much thanks for the suggestion.. My current platform is an ESX VM CentOS 5.5 (very minimal install and currently bind 9.6.2.. I can "dual home" it but need to really do some testing on bind listening on 2 IP addresses.. We were actually moving down this road.. (a new "box") I have an e

RE: rndc addzone/delzone in 9.7.2rc1 (was: rndc reconfig delays)

Seems to me that if you stick with this, a couple of things are necessary for manageability: o Some command to translate a zone file name to a view/zone name, and vice-versa. That would enable people to debug based on file contents... o A method to migrate zones from today's 'named.conf-config