Bind problems

[F. Even]

Comments in message.

On 9/10/03 7:34 PM, "Chefy Tim" <chefytim at metasoft.net> wrote:

> I have recently setup a RedHat 9 linux PDC with DHCP, DNS and Samba
> installed on it. 
> 
> I really have never setup DNS on Linux before and appear to be having some
> problems.
> 
> I have several Windows XP machines that have been successfully joined to the
> Linux "domain" and are connecting without any problems including a login
> script that maps to shares on the Linux box.
> 
> The Windows clients can ping the server with the friendly name but not the
> fully qualified domain name. DHCP also seems to be working flawlessly.
> 
> When a Windows machine boots up I get a couple of error messages in the
> system log of the Linux box like these.
> 
> ******************************************************************************
> **
> 
> Sep 10 19:24:41 server named[1581]: client 192.168.48.100#1036: updating
> zone 'thekitchen.com/IN': update failed: 'RRset exists (value dependent)'
> prerequisite not satisfied (NXRRSET)
> Sep 10 19:24:41 server named[1581]: client 192.168.48.100#1038: update
> 'thekitchen.com/IN' denied
> 
> ******************************************************************************
> **

You have some problems w/ your zone file.

> 
> Here is my named.conf file:
> 
> ## named.conf - configuration for bind
> #
> # Generated automatically by redhat-config-bind, alchemist et al.
> # Any changes not supported by redhat-config-bind should be put
> # in /etc/named.custom
> #
> controls {
>       inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> };
> 
> include "/etc/named.custom";
> 
> include "/etc/rndc.key";
> 
> 
> zone  "0.0.127.in-addr.arpa" {
>       type master;
>       file  "0.0.127.in-addr.arpa.zone";
> };
> zone  "48.168.192.in-addr.arpa" {
>       type master;
>       file  "48.168.192.in-addr.arpa.zone";
> };
> 
> 
> zone  "localhost" {
>       type master;
>       file  "localhost.zone";
> };
> zone  "thekitchen.com" {
>       type master;
>       file  "thekitchen.com.zone";
> };
> 
> 
> ******************************************************************************
> **
> Here is my forward zone file:
> $TTL 86400
> @       IN      SOA     192.168.48.2.  root.localhost (
>                       2 ; serial
>                       28800 ; refresh
>                       7200 ; retry
>                       604800 ; expire
>                       86400 ; ttl
>                       )
> 
> 
>       IN      NS      server.

How do you plan on resolving "server"?

> 
> @       IN      A       192.168.48.2
> 
> ******************************************************************************
> **
> Here is my reverse zone file:
> 
> 
> $TTL 86400
> @       IN      SOA     192.168.48.2.   root.localhost (
>                       5 ; serial
>                       28800 ; refresh
>                       7200 ; retry
>                       604800 ; expire
>                       86400 ; ttk
>                       )
> 
> 
> @       IN      NS      192.168.48.2.

This is wrong.  A name server needs to be a fully qualified domain name, not
an IP. 

> 2       IN      PTR     server.thekitchen.com.
> 
> 
> 
> ******************************************************************************
> **
> 
> 
> Also, do I need to keep the 127.0.0.1 (localhost) entries in these files?
> In other words, do I need a local zone?

It never hurts.

> Anyway, any help would be greatly appreciated.
> 
> Thanks,

Also...is 192.168.48.100 an XP machine on your network?  It appears that it
could be trying to dynamically update your zone with it's hostname.  It does
not look like you are configured for dynamic updates.  Disable that on the
XP client.