Results 1 to 10 of 10

Thread: Bind installation

  1. #1
    Join Date
    Jan 2009
    Posts
    19
    Rep Power
    6

    Default Bind installation

    I am trying to install bind on my RHEL server to resolve the issues of mot receiving mails because i am behind an ISP's router and a firewall.

    I've ran these codes:
    yum install bind
    yum install caching-nameserver
    cp named.caching-nameserver.conf named.conf (because i dont have a file called named.conf after bind installation).

    touch mydomain.com.zone
    touch mydomain.com.rev.zone

    chown root:named mydomain*


    Can anybody tell me what next to do?

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Follow the examples in Split DNS - Zimbra :: Wiki though you should not require the necessity to install a caching-nameserver.

  3. #3
    Join Date
    Jan 2009
    Posts
    19
    Rep Power
    6

    Default

    After installation of Bind an the configuration of the DNS;
    i did nslookup servername.mydomain.com and i got this message:
    Server: 192.168.2.100
    Address: 192.168.2.100#53

    ** server can't find servername.mydomain.com: NXDOMAIN


    what do i do?

  4. #4
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Check /var/log/messages for any BIND error messages.

  5. #5
    Join Date
    Jan 2009
    Posts
    19
    Rep Power
    6

    Default

    there are no errors on bind.

    what do i do

  6. #6
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Please post output from
    Code:
    cat /etc/hosts
    cat /etc/resolv.conf
    dig youdomain mx
    dig youdomain any
    host `hostname` <- note backticks and not single quotes
    Plus your BIND named.conf and the associated zone files.

  7. #7
    Join Date
    Jan 2009
    Posts
    19
    Rep Power
    6

    Default

    the output of cat /etc/hosts file:

    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1 alpha.paletteng.com alpha localhost.localdomain localhost
    ::1 localhost6.localdomain6 localhost6
    192.168.2.188 alpha.paletteng.com alpha


    the ouput from cat /etc/resolv.conf file is:

    search paletteng.com
    nameserver 192.168.2.100
    nameserver 192.168.2.188


    the output from dig mydomain.com is:

    ; <<>> DiG 9.3.4-P1 <<>> paletteng.com mx
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31715
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

    ;; QUESTION SECTION:
    ;paletteng.com. IN MX

    ;; ANSWER SECTION:
    paletteng.com. 14400 IN MX 0 paletteng.com.

    ;; AUTHORITY SECTION:
    paletteng.com. 6717 IN NS ns2.hostingseries43.net.
    paletteng.com. 6717 IN NS ns.hostingseries43.net.

    ;; ADDITIONAL SECTION:
    paletteng.com. 6717 IN A 85.13.243.2
    ns2.hostingseries43.net. 150247 IN A 85.13.243.3
    ns.hostingseries43.net. 150247 IN A 85.13.243.2

    ;; Query time: 3915 msec
    ;; SERVER: 192.168.2.100#53(192.168.2.100)
    ;; WHEN: Tue Feb 3 13:08:07 2009
    ;; MSG SIZE rcvd: 149

    the dig mydomain any gives:

    ; <<>> DiG 9.3.4-P1 <<>> paletteng.com any
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59774
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 2, ADDITIONAL: 3

    ;; QUESTION SECTION:
    ;paletteng.com. IN ANY

    ;; ANSWER SECTION:
    paletteng.com. 12890 IN MX 0 paletteng.com.
    paletteng.com. 5207 IN A 85.13.243.2
    paletteng.com. 5207 IN NS ns2.hostingseries43.net.
    paletteng.com. 5207 IN NS ns.hostingseries43.net.

    ;; AUTHORITY SECTION:
    paletteng.com. 5207 IN NS ns.hostingseries43.net.
    paletteng.com. 5207 IN NS ns2.hostingseries43.net.

    ;; ADDITIONAL SECTION:
    paletteng.com. 5207 IN A 85.13.243.2
    ns2.hostingseries43.net. 148737 IN A 85.13.243.3
    ns.hostingseries43.net. 148737 IN A 85.13.243.2

    ;; Query time: 4 msec
    ;; SERVER: 192.168.2.100#53(192.168.2.100)
    ;; WHEN: Tue Feb 3 13:33:17 2009
    ;; MSG SIZE rcvd: 193


    host `hostname` gives:

    Host alpha.paletteng.com not found: 3(NXDOMAIN)


    paletteng.com.rev.zone file

    $ORIGIN 2.168.192.in-addr.arpa. ;

    $TTL 86400 @ IN SOA alpha.paletteng.com. root.localhost. (

    2008020402 ; serial

    10800 ; REFRESH 3 hour

    10800 ; retry after 3 hours

    604800 ; expire after 1 week

    86400) ; Min TTL of 1 day 2.168.192.in-addr.arpa. NS alpha.paletteng.com.

    188.2.168.192.in-addr.arpa. IN PTR paletteng.com.

    paletteng.com.zone file:

    $ORIGIN paletteng.com.

    $TTL 3600 @ IN SOA alpha.paletteng.com. root.localhost. (

    2008020403 ; Serial 4char year 2mm 2dd 2vv

    10800 ; REFRESH

    10800 ; retry after 3 hours which forces it on the slave

    604800 ; expire after 1 week

    86400 ) ; minimum TTL of 1 day paletteng.com. IN NS alpha.paletteng.com. ;note paletteng.com. IN A 192.168.2.188

    www IN A 192.168.2.188

    site1.paletteng.com. IN A 192.168.2.188

    site2.paletteng.com. IN A 192.168.2.188

    localhost A 127.0.0.1



    the named.conf file is

    //
    // named.caching-nameserver.conf
    //
    // Provided by Red Hat caching-nameserver package to configure the
    // ISC BIND named(8) DNS server as a caching only nameserver
    // (as a localhost DNS resolver only).
    //
    // See /usr/share/doc/bind*/sample/ for example named configuration files.
    //
    // DO NOT EDIT THIS FILE - use system-config-bind or an editor
    // to create named.conf - edits to this file will be lost on
    // caching-nameserver package upgrade.
    //
    options {
    listen-on port 53 { 127.0.0.1; };
    listen-on-v6 port 53 { ::1; };
    directory "/var/named";
    dump-file "/var/named/data/cache_dump.db";
    statistics-file "/var/named/data/named_stats.txt";
    memstatistics-file "/var/named/data/named_mem_stats.txt";

    // Those options should be used carefully because they disable port
    // randomization
    // query-source port 53;
    // query-source-v6 port 53;

    allow-query { localhost; };
    };
    logging {
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    };
    };
    view localhost_resolver {
    match-clients { localhost; };
    match-destinations { localhost; };
    recursion yes;
    include "/etc/named.rfc1912.zones";
    };
    // named.rfc1912.zones:
    //
    // Provided by Red Hat caching-nameserver package
    //
    // ISC BIND named zone configuration for zones recommended by
    // RFC 1912 section 4.1 : localhost TLDs and address zones
    //
    // See /usr/share/doc/bind*/sample/ for example named configuration files.
    //
    zone "." IN {
    type hint;
    file "named.ca";
    };

    zone "localdomain" IN {
    type master;
    file "localdomain.zone";
    allow-update { none; };
    };

    zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

    zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };

    zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.ip6.arpa" IN {
    type master;
    file "named.ip6.local";
    allow-update { none; };
    };

    zone "255.in-addr.arpa" IN {
    type master;
    file "named.broadcast";
    allow-update { none; };
    };

    zone "0.in-addr.arpa" IN {
    type master;
    file "named.zero";
    allow-update { none; };
    };

  8. #8
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    The simple answer is, you have no A or MX records for your server. Please check the Split DNS article again and follow those instructions.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  9. #9
    Join Date
    Jan 2009
    Posts
    19
    Rep Power
    6

    Default

    the Split DNS document is not clear enough,

    I cant find my named.conf file after the installation of Bind and even if i create a named.conf file,i would nt know what the contents will be.

    Is there any other documentation better or GUI configuration?

  10. #10
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Read, read and read again ... Quick HOWTO : Ch18 : Configuring DNS - Linux Home Networking

    Before proceeding understand how and why BIND works as it will help you in the future.

Similar Threads

  1. Mail deferred with Connection timed out
    By Miklos Kalman in forum Administrators
    Replies: 7
    Last Post: 11-17-2012, 05:11 AM
  2. Replies: 4
    Last Post: 07-29-2008, 12:14 PM
  3. Installation Issues - SLES 10_Zimbra 5.0 Beta 3
    By rhartman in forum Installation
    Replies: 3
    Last Post: 01-14-2008, 06:18 AM
  4. [SOLVED] Bind crash after Zimbra installation
    By druid in forum Installation
    Replies: 3
    Last Post: 10-04-2007, 12:34 AM
  5. Installation problem
    By sywong70 in forum Installation
    Replies: 5
    Last Post: 11-07-2005, 08:01 PM

Posting Permissions

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