Find the answer to your Linux question:
Results 1 to 3 of 3
HI All, I am trying to setup DNS on my centOS server. I am using bind software to setup DNS. The following errors have getting. ================================================== ===== Error in named ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Apr 2011
    Posts
    2

    Domain name server installation issue in centOS


    HI All,

    I am trying to setup DNS on my centOS server.
    I am using bind software to setup DNS.
    The following errors have getting.

    ================================================== =====
    Error in named configuration:
    zone localdomain/IN: loaded serial 42
    zone localhost/IN: loaded serial 42
    zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    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: loaded serial 1997022700
    zone 255.in-addr.arpa/IN: loaded serial 42
    zone 0.in-addr.arpa/IN: loaded serial 42
    ================================================== =====

    Thank you in advanced

  2. #2
    Just Joined!
    Join Date
    Apr 2011
    Posts
    2

    no one is helping me

    Hello Guys,

    still i am getting following errors


    Error in named configuration:
    zone localdomain/IN: loaded serial 42
    zone localhost/IN: loaded serial 42
    zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    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: loaded serial 1997022700
    zone 255.in-addr.arpa/IN: loaded serial 42
    zone 0.in-addr.arpa/IN: loaded serial 42
    dns_rdata_fromtext: /var/named/test.com.zone:7: near eol: unexpected end of input
    zone test.com/IN: loading master file /var/named/test.com.zone: unexpected end of input
    internal/test.com/IN: unexpected end of input
    dns_rdata_fromtext: /var/named/test.com.zone:7: near eol: unexpected end of input
    zone test.com/IN: loading master file /var/named/test.com.zone: unexpected end of input
    external/test.com/IN: unexpected end of input



    Please check bellow my configuration files

    named.conf
    Code:
    include "/etc/rndc.key";
    
    controls {
    	inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
    };
    
    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;
    
        /* We no longer enable this by default as the dns posion exploit
            has forced many providers to open up their firewalls a bit */
    
        // Put files that named is allowed to write in the data/ directory:
        directory                "/var/named"; // the default
        pid-file                 "/var/run/named/named.pid";
        dump-file                "data/cache_dump.db";
        statistics-file          "data/named_stats.txt";
       /* memstatistics-file     "data/named_mem_stats.txt"; */
        allow-transfer {"none";};
    };
    
    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         { 127.0.0.0/24; };
        match-destinations    { localhost; };
        recursion yes;
    
        zone "." IN {
            type hint;
            file "/var/named/named.ca";
        };
    
        /* 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 "/var/named/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;
    
        zone "." IN {
            type hint;
            file "/var/named/named.ca";
        };
    
        // include "/var/named/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 "test.com" {
    	type master;
    	file "/var/named/test.com.zone";
    };
    
    
    };
    
    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:
     */
        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:
        zone "." IN {
            type hint;
            file "/var/named/named.ca";
        };
    
        // These are your "authoritative" external zones, and would probably
        // contain entries for just your web and mail servers:
    
        // BEGIN external zone entries
    
    
    zone "test.com" {
    	type master;
    	file "/var/named/test.com.zone";
    };
    
    
    };
    test.com.zone
    Code:
    $TTL 14400
    @      86400	IN      SOA     ns1.test.com. (
    		2011031402	; serial, todays date+todays
    		86400		; refresh, seconds
    		7200		; retry, seconds
    		3600000		; expire, seconds
    		86400 )		; minimum, seconds
    
    test.com. 86400 IN NS ns1.test.com.
    test.com. 86400 IN NS ns2.test.com.
    
    
    test.com. IN A 204.12.231.44
    
    localhost.test.com. IN A 127.0.0.1
    
    test.com. IN MX 0 test.com.
    
    www IN CNAME test.com.
    ftp IN A 204.12.231.44
    named.rfc1912.zones
    Code:
    // named.rfc1912.zones:
    //
    // ISC BIND named zone configuration for zones recommended by
    // RFC 1912 section 4.1 : localhost TLDs and address zones
    // 
    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; };
    };

  3. #3
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    The error is telling you the problem all you need to do is read it.

    dns_rdata_fromtext: /var/named/test.com.zone:7: near eol: unexpected end of input
    7 is the line number and the rest is telling you what the problem is. In this case it was expecting more then what it got.

    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
  •