Find the answer to your Linux question:
Results 1 to 4 of 4
My System Settings ; [root@winner ~]# hostname winner.com [root@winner ~]# ------------------------------------------------- [root@winner ~]# rpm -qa | grep bind bind-utils-9.3.3-7.el5 bind-9.3.3-7.el5 bind-libbind-devel-9.3.3-7.el5 ypbind-1.19-7.el5 kdebindings-3.5.4-1.fc6 bind-libs-9.3.3-7.el5 bind-devel-9.3.3-7.el5 bind-chroot-9.3.3-7.el5 bind-sdb-9.3.3-7.el5 [root@winner ~]# ------------------------------------------------- ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2005
    Location
    Sivakasi, Tamilnadu, India
    Posts
    17

    DNS Problem


    My System Settings ;

    [root@winner ~]# hostname
    winner.com
    [root@winner ~]#
    -------------------------------------------------
    [root@winner ~]# rpm -qa | grep bind
    bind-utils-9.3.3-7.el5
    bind-9.3.3-7.el5
    bind-libbind-devel-9.3.3-7.el5
    ypbind-1.19-7.el5
    kdebindings-3.5.4-1.fc6
    bind-libs-9.3.3-7.el5
    bind-devel-9.3.3-7.el5
    bind-chroot-9.3.3-7.el5
    bind-sdb-9.3.3-7.el5
    [root@winner ~]#
    -------------------------------------------------
    [root@winner ~]# vi /var/named/chroot/etc/named.conf

    //
    // Sample named.conf BIND DNS server 'named' configuration file
    // for the Red Hat BIND distribution.
    //
    // See the BIND Administrator's Reference Manual (ARM) for details, in:
    // file:///usr/share/doc/bind-*/arm/Bv9ARM.html
    // Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
    // its manual.
    //
    options
    {
    /* make named use port 53 for the source of all queries, to allow
    * firewalls to block all ports except 53:
    */
    query-source port 53;
    query-source-v6 port 53;

    // Put files that named is allowed to write in the data/ directory:
    directory "/var/named"; // the default
    dump-file "data/cache_dump.db";
    statistics-file "data/named_stats.txt";
    memstatistics-file "data/named_mem_stats.txt";
    listen-on port 53 { any; };

    };
    logging
    {
    /* If you want to enable debugging, eg. using the 'rndc trace' command,
    * named will try to write the 'named.run' file in the $directory (/var/named).
    * By default, SELinux policy does not allow named to modify the /var/named directory,
    * so put the default debug log file in data/ :
    */
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    };
    };
    //
    // All BIND 9 zones are in a "view", which allow different zones to be served
    // to different types of client addresses, and for options to be set for groups
    // of zones.
    //
    // By default, if named.conf contains no "view" clauses, all zones are in the
    // "default" view, which matches all clients.
    //
    // If named.conf contains any "view" clause, then all zones MUST be in a view;
    // so it is recommended to start off using views to avoid having to restructure
    // your configuration files in the future.
    //
    view "localhost_resolver"
    {
    /* This view sets up named to be a localhost resolver ( caching only nameserver ).
    * If all you want is a caching-only nameserver, then you need only define this view:
    */
    match-clients { localhost; };
    match-destinations { localhost; };
    recursion yes;
    # all views must contain the root hints zone:
    include "/etc/named.root.hints";

    /* these are zones that contain definitions for all the localhost
    * names and addresses, as recommended in RFC1912 - these names should
    * ONLY be served to localhost clients:
    */
    include "/etc/named.rfc1912.zones";
    };
    view "internal"
    {
    /* This view will contain zones you want to serve only to "internal" clients
    that connect via your directly attached LAN interfaces - "localnets" .
    */
    match-clients { localnets; };
    match-destinations { localnets; };
    recursion yes;
    // all views must contain the root hints zone:
    include "/etc/named.root.hints";

    // include "named.rfc1912.zones";
    // you should not serve your rfc1912 names to non-localhost clients.

    // These are your "authoritative" internal zones, and would probably
    // also be included in the "localhost_resolver" view above :

    zone "my.internal.zone" {
    type master;
    file "my.internal.zone.db";
    };
    zone "winner.com.zone" {
    type master;
    file "winner.com.zone.db";
    };
    zone "100.180.in-addr.arpa.zone" {
    type master;
    file "100.180.in-addr.arpa.zone.db";
    };
    zone "my.slave.internal.zone" {
    type slave;
    file "slaves/my.slave.internal.zone.db";
    masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
    // put slave zones in the slaves/ directory so named can update them
    };
    zone "my.ddns.internal.zone" {
    type master;
    allow-update { key ddns_key; };
    file "slaves/my.ddns.internal.zone.db";
    // put dynamically updateable zones in the slaves/ directory so named can update them
    };
    };
    key ddns_key
    {
    algorithm hmac-md5;
    secret "2TqnBG3C4xl15cf9nqGKnDNIAwCXuVS6vyIlSV00lWbRKqdVw G74CRKqJzdF";
    };
    view "external"
    {
    /* This view will contain zones you want to serve only to "external" clients
    * that have addresses that are not on your directly attached LAN interface subnets:
    */
    match-clients { !localnets; !localhost; };
    match-destinations { !localnets; !localhost; };

    recursion no;
    // you'd probably want to deny recursion to external clients, so you don't
    // end up providing free DNS service to all takers

    // all views must contain the root hints zone:
    include "/etc/named.root.hints";

    // These are your "authoritative" external zones, and would probably
    // contain entries for just your web and mail servers:

    zone "my.external.zone" {
    type master;
    file "my.external.zone.db";
    };
    };
    -----------------------------------------------------------
    [root@winner ~]# vi /var/named/chroot/var/named/winner.com.zone.db

    $TTL 86400
    @ IN SOA winner.com. hostmaster.winner.com. (
    42 ; serial (d. adams)
    3H ; refresh
    15M ; retry
    1W ; expiry
    1D ) ; minimu
    IN NS winner.com.
    winner.com IN A 180.100.103.62
    ------------------------------------------------------------
    [root@winner ~]# vi /var/named/chroot/var/named/100.180.in-addr.arpa.zone.db

    $TTL 86400
    @ IN SOA winner.com. hostmaster.winner.com. (
    42 ; serial (d. adams)
    3H ; refresh
    15M ; retry
    1W ; expiry
    1D ) ; minimum
    NS winner.com.
    1 IN PTR winner.com.
    --------------------------------------------------------------
    [root@winner ~]# vi /etc/hosts

    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    180.100.103.62 winner.com
    .................................................. ............
    [root@winner ~]# vi /etc/resolv.conf
    search winner.com
    nameserver 180.100.103.62
    .................................................. ............
    [root@winner ~]# iptables -L

    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination
    [root@winner ~]#
    ---------------------------------------------------------------[root@winner ~]# dig localhost

    ; <<>> DiG 9.3.3rc2 <<>> localhost
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46176
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;localhost. IN A

    ;; ANSWER SECTION:
    localhost. 86400 IN A 127.0.0.1

    ;; AUTHORITY SECTION:
    localhost. 86400 IN NS localhost.

    ;; ADDITIONAL SECTION:
    localhost. 86400 IN AAAA ::1

    ;; Query time: 0 msec
    ;; SERVER: 180.100.103.62#53(180.100.103.62)
    ;; WHEN: Tue Sep 23 12:40:28 2008
    ;; MSG SIZE rcvd: 85
    --------------------------------------------------------------
    [root@winner ~]# dig winner.com

    ; <<>> DiG 9.3.3rc2 <<>> winner.com
    ;; global options: printcmd
    ;; connection timed out; no servers could be reached
    [root@winner ~]#
    ----------------------------------------------------------

    Why?

    Please reply.

  2. #2
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    Run the following commands and post the output.

    Code:
    /usr/sbin/named-checkconf
    /usr/sbin/named-checkzone winner.com /<path>/winner.com.zone.db

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  3. #3
    Just Joined!
    Join Date
    Aug 2005
    Location
    Sivakasi, Tamilnadu, India
    Posts
    17
    Hello Sir

    There is the output

    [root@winner ~]# /usr/sbin/named-checkconf
    [root@winner ~]# /usr/sbin/named-checkconf winner.com /var/named/chroot/var/named/winner.com.zone.db
    none:0: open: winner.com: file not found
    [root@winner ~]#

  4. #4
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    There could be the first problem. What does the following command show:

    Code:
    locate winner.com.*

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

Posting Permissions

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