Find the answer to your Linux question:
Results 1 to 2 of 2
Locally, forward lookups do not work, but reverse lookups do when using BIND 9.3.2 on OpenSuSE. Any help would be appreciated. Config files and respective outcomes printed below. --mjr tux:~ ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    May 2007
    Posts
    2

    BIND Reverse Lookups OK, Forward not so much


    Locally, forward lookups do not work, but reverse lookups do when using BIND 9.3.2 on OpenSuSE. Any help would be appreciated.

    Config files and respective outcomes printed below.

    --mjr


    tux:~ # cat /var/lib/named/master/ebrs-i.org.hosts
    $TTL 86400 ;

    ebrs-i.org. IN SOA tux.ebrs-i.org. root.tux.ebrs-i.org. (
    2007052501 ; serial
    28800 ; refresh
    7200 ; retry
    604800 ; expiry
    3600 ) ; minimum

    IN NS tux
    IN MX 10 tux
    IN A 192.168.0.50
    tux IN A 192.168.0.1
    wrt54g IN A 192.168.0.20
    printer IN A 192.168.0.21
    adm IN A 192.168.0.50
    office IN A 192.168.0.51
    treasurer IN A 192.168.0.52
    meeting IN A 192.168.0.53
    conference IN A 192.168.0.54
    radio IN A 192.168.0.55
    kitchen IN A 192.168.0.56

    ebrs IN CNAME adm
    www IN CNAME adm

    tux:~ # cat /var/lib/named/master/0.168.192.in-addr.arpa
    $ORIGIN 0.168.192.in-addr.arpa.
    $TTL 86400
    @ IN SOA tux.ebrs-i.org. root.tux.ebrs-i.org. (
    2007052100 ; serial
    21600 ; refresh
    3600 ; retry
    604800 ; expiry
    86500 ) ; minimum
    IN NS tux.ebrs-i.org.
    1 IN PTR tux.ebrs-i.org.
    20 IN PTR wrt54g.ebrs-i.org.
    21 IN PTR printer.ebrs-i.org.
    50 IN PTR adm.ebrs-i.org.
    51 IN PTR office.ebrs-i.org.
    52 IN PTR treasurer.ebrs-i.org.
    53 IN PTR meeting.ebrs-i.org.
    54 IN PTR conference.ebrs-i.org.
    55 IN PTR radio.ebrs-i.org.
    56 IN PTR kitchen.ebrs-i.org.

    tux:~ # cat /etc/named.conf
    # Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
    # All rights reserved.
    #
    # Author: Frank Bodammer, Lars Mueller <lmuelle@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.

    acl local-network {
    192.168.0.0/24;
    127.0.0.0/24;
    };

    key "rndc-key" {
    algorithm hmac-md5;
    secret "<rndc key>";
    };


    controls {
    inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
    };

    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; };
    #listen-on port 53 {127.0.0.1 192.168.0.1; };
    # 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 { local-network; };
    allow-recursion { local-network; };

    # 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;
    include "/etc/named.d/forwarders.conf";
    forward first;
    };

    # 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; };
    #
    # # 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; };
    #};

    logging {
    category xfer-in { log_syslog; };
    category xfer-out { log_syslog; };
    category default { log_syslog; };
    channel log_syslog { syslog; };
    };

    # 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 "localhost" in {
    type master;
    file "localhost.zone";
    };

    zone "0.0.127.in-addr.arpa" in {
    type master;
    file "127.0.0.zone";
    };

    zone "." in {
    type hint;
    file "root.hint";
    };

    # 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";

    # 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.

    zone "ebrs-i.org " in {
    type master;
    file "/var/lib/named/master/ebrs-i.org.hosts";
    allow-transfer { any; };
    };

    zone "0.168.192.in-addr.arpa" in {
    allow-transfer { any; };
    file "master/0.168.192.in-addr.arpa";
    type master;
    };

    tux:~ # nslookup adm.ebrs-i.org.
    Server: 192.168.0.1
    Address: 192.168.0.1#53

    ** server can't find adm.ebrs-i.org: NXDOMAIN

    tux:~ # nslookup adm
    Server: 192.168.0.1
    Address: 192.168.0.1#53

    ** server can't find adm: NXDOMAIN

    tux:~ # nslookup 192.168.0.50
    Server: 192.168.0.1
    Address: 192.168.0.1#53

    50.0.168.192.in-addr.arpa name = adm.ebrs-i.org.

    tux:~ #

    -------
    Or, my favorite, on Windows:

    C:\>nslookup 192.168.0.1
    Server: tux.ebrs-i.org
    Address: 192.168.0.1

    Name: tux.ebrs-i.org
    Address: 192.168.0.1


    C:\>nslookup tux.ebrs-i.org
    Server: tux.ebrs-i.org
    Address: 192.168.0.1

    *** tux.ebrs-i.org can't find tux.ebrs-i.org: Non-existent domain

    C:\>

  2. #2
    Just Joined!
    Join Date
    May 2007
    Posts
    2
    I changed logging options and the zone file around a bit, here's what I came up with:

    /var/log/messages
    May 25 22:18:39 tux named[31278]: loading configuration from '/etc/named.conf'
    May 25 22:18:39 tux named[31278]: listening on IPv6 interfaces, port 53
    May 25 22:18:39 tux named[31278]: listening on IPv4 interface lo, 127.0.0.1#53
    May 25 22:18:39 tux named[31278]: listening on IPv4 interface eth1, 192.168.0.1#53
    May 25 22:18:39 tux named[31278]: /etc/named.d/forwarders.conf:7: no forwarders seen; disabling forwarding
    May 25 22:18:39 tux named[31278]: /etc/named.d/forwarders.conf:7: no forwarders seen; disabling forwarding
    May 25 22:18:39 tux named[31278]: command channel listening on 127.0.0.1#953
    May 25 22:18:39 tux named[31278]: logging channel 'query_logging' file '/var/log/named_querylog': permission denied
    May 25 22:18:39 tux named[31278]: zone ebrs-i.org\032/IN: has 0 SOA records
    May 25 22:18:39 tux named[31278]: zone ebrs-i.org\032/IN: has no NS records

    /var/lib/named/master/ebrs-i.org.hosts
    $TTL 86400 ;
    $ORIGIN ebrs-i.org.

    @ IN SOA tux.ebrs-i.org. root.tux.ebrs-i.org. (
    2007052501 ; serial
    28800 ; refresh
    7200 ; retry
    604800 ; expiry
    3600 ) ; minimum

    IN NS tux.ebrs-i.org.
    IN MX 10 tux.ebrs-i.org.
    tux IN A 192.168.0.1
    IN A 192.168.0.50
    wrt54g IN A 192.168.0.20
    printer IN A 192.168.0.21
    adm IN A 192.168.0.50
    office IN A 192.168.0.51
    treasurer IN A 192.168.0.52
    meeting IN A 192.168.0.53
    conference IN A 192.168.0.54
    radio IN A 192.168.0.55
    kitchen IN A 192.168.0.56

    ebrs IN CNAME adm
    www IN CNAME adm

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •