Trying to do reverse lookups, but crashing named instead.

[Adam Tkac]

On 01/19/2012 09:18 PM, Stack Kororā wrote:
> Hello,
>
> The dhcpd mailinglist sent me your way with a problem I am having with
> named/dhcpd.
>
> The problem I have is that I can not seem to get reverse hostname lookups
> in my PXEboot, which means my PXEboot clients think they are localhost.
>
> The problem that may be more relevant to the BIND list is that I can
> reproducibly cause named to crash with a nasty looking error.
>
> I am running on Scientific Linux 6.2 (rolling) with
> bind-9.7.3-8.P3.el6.x86_64 and dhcp-4.1.1-25.P1.el6_2.1.x86_64.
>
> In my log files below what I did was run `service named restart&&  service
> dhcpd restart` then promptly start a PXEboot. The log file starts with the
> first named message. Please let me know if there are other files or any
> other information you would care for. The crash always starts with this
> line first "failed to create new zone: already exists".
>
> Files are attached in this order:
> dhcpd.conf
> named.conf
> resolv.conf
> project
> project.reverse
> messages
> rndc.key<- Nope, don't care that I am posting this. I know it is supposed
> to be secret but this is a virtual machine test lab with zero importance
> and isn't connected to the internet.
>
>
> There are two other logging files mentioned in the conf files:
> /var/log/named-auth.info never has any information in it.
> /var/log/update-debug.log mostly complains about this:
> update: info: client 127.0.0.1#46599: updating zone 'project.local/IN':
> update unsuccessful: aa001.project.local: 'name not in use' prerequisite
> not satisfied (YXDOMAIN)
>
> I know the error says that it thinks the domain does not exist. I have read
> the FAQ and the rfc2136.txt, yet I still don't understand why it thinks
> that.
>
> Any help is appreciated.
> Thanks!

This indicates a bug in named or in the bind-dyndb-ldap plugin. Please 
open a bug report in Red Hat bugzilla (https://bugzilla.redhat.com).

Regards, Adam