Dynamic Updates

[Kevin Darcy]

I don't think there's anything you can do on your side to fix this. The zones
appear to be misconfigured on the 192.168.0.131 server. NXDOMAIN means,
basically, "I know nothing of this name". A correctly-configured master would
never answer that about any of the zones it serves.


- Kevin

Godfried Duodu wrote:

> We are testing  interoperability between bind-9.2.1 on RH9 servers and a =
> Windows 2000 server (slave). I created zones ( _tcp, _udp, _msdcs, =
> _sites)=20
> for the windows 2000 server ala Cricket Liu recommendation in his article =
> in Linuxgazette.
>
> The logs on the slave server (ldapserver)shows the information below:
>
> Jul 29 04:51:35 ldapserver named[721]: Jul 29 04:51:35.344general:  info: =
> zone _udp.duoduman.com/IN: refresh: unexpected rcode (NXDOMAIN)  from =
> master 192.168.0.131#53
> Jul 29 04:51:35 ldapserver named[721]: Jul 29 04:51:35.348general:  info: =
> zone _sites.duoduman.com/IN: refresh: unexpected rcode  (NXDOMAIN) from =
> master 192.168.0.131#53
> Jul 29 04:51:35 ldapserver named[721]: Jul 29 04:51:35.350general:  info: =
> zone _tcp.duoduman.com/IN: refresh: unexpected rcode (NXDOMAIN)  from =
> master 192.168.0.131#53
> Jul 29 04:51:35 ldapserver named[721]: Jul 29 04:51:35.352general:  info: =
> zone _msdcs.duoduman.com/IN: refresh: unexpected rcode  (NXDOMAIN) from =
> master 192.168.0.131#53
>
> Could anyone suggest what I need to on the master server to eliminate =
> those error messages?=20
> Thanks in advance.