bind not responding for name resolution

[Neil Muller]

Hi Kevin,

I've included details of my resolv.conf and nsswitch.conf as well 
named's output in /var/log/messages and output from dig and ping. I 
still can't see where the problem is occurring as dig and nslookup 
return information as expected.

Any ideas are welcome.

Neil


Kevin Darcy wrote:

>Neil Muller wrote:
>
>  
>
>>Hi,
>>
>>I have to set up a name server for a private network. The os is SUSE 9.2 
>>PRO with the standard SUSE packages of bind 9.2.4-3  and dhcpd 3.0.1. I 
>>have set up dhcpd with ddns and that is working well and notifying bind 
>>but I cannot get bind to respond to any name resolution  requests (eg. 
>>ping myserver).
>>
>>    
>>
>
>Hmm... How do you know that dhcpd is updating DNS if you can't even 
>query DNS?
>
When I check the zone files and the zone .jnl files I can see the 
entries for workstations that have dhcp addresses therefor I assumed 
that the communications from dhcpd to bind was working ok..

>
>By "cannot get bind to respond", do you mean the queries time out? 
>
If I "ping server1" I get "Unknown host" messages but if I "nslookup 
server1" I get server1's ipaddress information. I have attached some of 
the output from /var/log/messages a dig and a ping.

>What 
>is your /etc/resolv.conf set to? 
>
search mydomain.local
nameserver 127.0.0.1
nameserver 10.0.0.250

>Your /etc/nsswitch.conf (or 
>

hosts: files dns

>equivalent)? Does "dig" against the nameserver work? Are you doing the 
>queries locally or from some other client? According to your config, 
>you're only listening on 127.0.0.1 and 10.0.0.250; is the client trying 
>to query some other address besides those two? Is there anything in the 
>logs at named startup time?
>
>                                                                         
>                                             - Kevin
>
>  
>
>>I haven't included the DHCP_UPDATER key but the ddns update seems to be 
>>received ok because it is registered in the zone journal files.
>>
>>named and dhcpd are both running chrooted. My named config files are 
>>attached. I hope someone can throw some light on this.
>>
>>TIA
>>
>>Neil
>>
>>
>>
>>My named.conf looks like this:
>>
>>
>>**** start of named .conf ****
>>
<snip>

>>
>>
>>My zone files are:
>>
>>**** start of domain.local zone file ****
>>
<snip>
****
**** named log messages on startup
****
Mar 19 09:27:53 server1 named[8882]: starting BIND 9.2.4 -t 
/var/lib/named -u named
Mar 19 09:27:53 server1 named[8882]: using 1 CPU
Mar 19 09:27:53 server1 named[8882]: loading configuration from 
'/etc/named.conf'
Mar 19 09:27:53 server1 named[8882]: listening on IPv6 interfaces, port 53
Mar 19 09:27:53 server1 named[8882]: listening on IPv4 interface lo, 
127.0.0.1#53
Mar 19 09:27:53 server1 named[8882]: binding TCP socket: address in use
Mar 19 09:27:53 server1 named[8882]: listening on IPv4 interface eth0, 
10.0.0.250#53
Mar 19 09:27:53 server1 named[8882]: binding TCP socket: address in use
Mar 19 09:27:53 server1 named[8882]: command channel listening on 
127.0.0.1#953
Mar 19 09:27:53 server1 named[8882]: command channel listening on ::1#953

****
**** example dig server1.mydomain.local MX  output
****
server1:~ # dig server1.mydomain.local MX

; <<>> DiG 9.2.4 <<>> server1.mydomain.local MX
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61476
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;server1.mydomain.local.   IN      MX

;; AUTHORITY SECTION:
mydomain.local.       86400   IN      SOA     server1.mydomain.local. 
root.server1.mydomain.local. 2005031210 10800 3600 604800 86400

;; Query time: 22 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Mar 19 09:30:32 2005
;; MSG SIZE  rcvd: 86



****
**** example of ping server1.mydomain.local output
****
server1:~ # ping server1.mydomain.local
ping: unknown host server1.mydomain.local


****
**** dhcpd.leases
****
# All times in this file are in UTC (GMT), not your local timezone.   
This is
# not a bug, so please don't ask about it.   There is no portable way to
# store leases in the local timezone, so please don't request this as a
# feature.   If this is inconvenient or confusing to you, we sincerely
# apologize.   Seriously, though - don't ask.
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-V3.0.1

lease 10.0.0.100 {
  starts 5 2005/03/18 22:39:31;
  ends 6 2005/03/19 02:39:31;
  binding state active;
  next binding state free;
  hardware ethernet 00:11:24:73:a8:7e;
  uid "\000host2";
  set ddns-rev-name = "100.0.0.10.in-addr.arpa.";
  set ddns-txt = "31d9637a08c16513a4e74f5395b4d06cda";
  set ddns-fwd-name = "host1.mydomain.local";
  client-hostname "host1";
}