bind not responding for name resolution

Thu Mar 17 00:10:15 UTC 2005

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?

By "cannot get bind to respond", do you mean the queries time out? What 
is your /etc/resolv.conf set to? Your /etc/nsswitch.conf (or 
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 ****
>
># Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
># All rights reserved.
>#
># Author: Frank Bodammer, Lars Mueller <lmuelle at suse.de>
>#
># /etc/named.conf
>#
># This is a sample configuration file for the name server BIND 9.  It 
>works as
># a caching only name server without modification.
>#
># A sample configuration for setting up your own domain can be found in
># /usr/share/doc/packages/bind/sample-config.
>#
># A description of all available options can be found in
># /usr/share/doc/packages/bind/misc/options.
>
>options {
>
>    # The directory statement defines the name server's working directory
>
>    directory "/var/lib/named";
>
>    # Write dump and statistics file to the log subdirectory.  The
>    # pathenames are relative to the chroot jail.
>
>    dump-file "/var/log/named_dump.db";
>    statistics-file "/var/log/named.stats";
>   
>    # The forwarders record contains a list of servers to which queries
>    # should be forwarded.  Enable this line and modify the IP address to
>    # your provider's name server.  Up to three servers may be listed.
>
>    #forwarders { 192.0.2.1; 192.0.2.2; };
>
>    # Enable the next entry to prefer usage of the name server declared in
>    # the forwarders section.
>
>    #forward first;
>
>    # The listen-on record contains a list of local network interfaces to
>    # listen on.  Optionally the port can be specified.  Default is to
>    # listen on all interfaces found on your system.  The default port is
>    # 53.
>
>    listen-on port 53 { 127.0.0.1; 10.0.0.250; };
>
>    # The listen-on-v6 record enables or disables listening on IPv6
>    # interfaces.  Allowed values are 'any' and 'none' or a list of
>    # addresses.
>
>    listen-on-v6 { any; };
>
>    # The next three statements may be needed if a firewall stands between
>    # the local server and the internet.
>
>    query-source address * port 53;
>    transfer-source * port 53;
>    notify-source * port 53;
>
>    # The allow-query record contains a list of networks or IP addresses
>    # to accept and deny queries from. The default is to allow queries
>    # from all hosts.
>
>    #allow-query { 127.0.0.1; };
>
>    # If notify is set to yes (default), notify messages are sent to other
>    # name servers when the the zone data is changed.  Instead of setting
>    # a global 'notify' statement in the 'options' section, a separate
>    # 'notify' can be added to each zone definition.
>
>    notify no;
>};
>
># To configure named's logging remove the leading '#' characters of the
># following examples.
>logging {
>    # Log queries to a file limited to a size of 100 MB.
>    channel query_logging {
>        file "/var/log/named_querylog"
>            versions 3 size 100M;
>        print-time yes;            // timestamp log entries
>    };
>    category queries {
>        query_logging;
>    };
>
>    # Or log this kind alternatively to syslog.
>    channel syslog_queries {
>        syslog user;
>        severity info;
>    };
>    category queries { syslog_queries; };
>
>    channel update_debug {
>        file "/var/log/update-debug.log";
>        severity debug 3;
>        print-category yes;
>        print-severity yes;
>        print-time     yes;
>    };
>    category update { update_debug; };
>
>    channel security_info {
>        file "/var/log/named-authinfo.log";
>        severity info;
>        print-category yes;
>        print-severity yes;
>        print-time     yes;
>    };
>    category security { security_info; };
>
>    # Log general name server errors to syslog.
>    channel syslog_errors {
>        syslog user;
>        severity error;
>    };
>    category default { syslog_errors;  };
>
>    # Don't log lame server messages.
>    category lame-servers { null; };
>};
>#
># The following zone definitions don't need any modification.  The first one
># is the definition of the root name servers.  The second one defines
># localhost while the third defines the reverse lookup for localhost.
>
>zone "." in {
>    type hint;
>    file "root.hint";
>};
>
>zone "localhost" in {
>    type master;
>    file "localhost.zone";
>};
>
>zone "0.0.127.in-addr.arpa" in {
>    type master;
>    file "127.0.0.zone";
>};
>
># Include the meta include file generated by createNamedConfInclude.  This
># includes all files as configured in NAMED_CONF_INCLUDE_FILES from
># /etc/sysconfig/named
>
>include "/etc/named.conf.include";
>
>
>zone "mydomain.local" in {
>    file "dyn/mydomain.local.zone";
>    type master;
>    allow-update { key DHCP_UPDATER; };
>};
>zone "0.0.10.in-addr.arpa" in {
>    file "dyn/10.0.0.zone";
>    type master;
>    allow-update { key DHCP_UPDATER; };
>};
>
># You can insert further zone records for your own domains below or create
># single files in /etc/named.d/ and add the file names to
># NAMED_CONF_INCLUDE_FILES.
># See /usr/share/doc/packages/bind/README.SUSE for more details.
>
>**** end of named.conf *****
>
>
>
>My zone files are:
>
>**** start of domain.local zone file ****
>
>$ORIGIN .
>$TTL 86400    ; 1 day
>mydomain.local    IN SOA    server1.mydomain.local. 
>root.server1.mydomain.local. (
>                2005031207 ; serial
>                10800      ; refresh (3 hours)
>                3600       ; retry (1 hour)
>                604800     ; expire (1 week)
>                86400      ; minimum (1 day)
>                )
>            NS    server1.mydomain.local.
>            MX    10 mail.mydomain.local.
>$ORIGIN mydomain.local.
>mydomain.local    A    10.0.0.250
>$ORIGIN mydomain.local.mydomain.local.
>server1        A    10.0.0.250
>server2            A    10.0.0.249
>$ORIGIN mydomain.local.
>localhost        A    127.0.0.1
>mail            CNAME    mydomain.local
>news            CNAME    mydomain.local
>ns            A    10.0.0.250
>server1        A    10.0.0.250
>server2            A    10.0.0.249
>www            A    10.0.0.250
>
>
>*****************
>
>**** start of reverse zone ****
>$ORIGIN .
>$TTL 604800    ; 1 week
>0.0.10.in-addr.arpa    IN SOA    server1.mydomain.local. 
>root.server1.mydomain.local. (
>                45         ; serial
>                172800     ; refresh (2 days)
>                14400      ; retry (4 hours)
>                3628800    ; expire (6 weeks)
>                604800     ; minimum (1 week)
>                )
>            NS    server1.
>$ORIGIN 0.0.10.in-addr.arpa.
>249            PTR    server2.
>            PTR    server2.mydomain.local.
>250            PTR    mydomain.local.
>            PTR    server1.
>            PTR    server1.mydomain.local.
>
>
>
>
>
>
>
>
>
>  
>