The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

named fails repeatedly...

Discussion in 'General Discussion' started by HorburySchool, Jul 30, 2008.

  1. HorburySchool

    HorburySchool Active Member

    Joined:
    Dec 14, 2007
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    6
    Have updated from Freebsd 6.3-RELEASE to 7.0-RELEASE, and stumbled across an issue with named that I can't get my head round...

    Have tried /scripts/fixrndc and /scripts/rebuildnamedconf, both produce same error as follows:

    Code:
    bigsis# /scripts/rebuildnamedconf
    [cPScript::Sys]: empty domain name must have a valid TLD label
    [cPScript::Sys]: localhost-forward domain name must have a valid TLD label
    [cPScript::Sys]: localhost-reverse domain name must have a valid TLD label
    Controls section not found, adding ...
    Adding controls clause ...
    Updating named.root to /etc/namedb/named.root
    Updating master/localhost-forward.db to /etc/namedb/localhost-forward.db
    Updating master/localhost-reverse.db to /etc/namedb/localhost-reverse.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/localhost-reverse.db to /etc/namedb/localhost-reverse.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    Updating master/empty.db to /etc/namedb/empty.db
    !! fixrndc experienced an error. No changes were made to /etc/namedb/named.conf
    /etc/namedb/named.conf.fixrndc:120: unknown option 'zone'
    /etc/namedb/named.conf.fixrndc:284: unexpected token near end of file
    

    Check of /var/log/messages gives the following:

    Code:
    Jul 30 14:48:16 bigsis root: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    Jul 30 14:48:56 bigsis marci: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    Jul 30 14:55:26 bigsis marci: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    Jul 30 14:56:39 bigsis root: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    Jul 30 15:05:02 bigsis root: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    Jul 30 15:10:13 bigsis marci: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    Jul 30 15:13:25 bigsis root: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named
    
    First issue I spot there is that it's correct... it can't run /usr/local/sbin/named cos it ain't there - it's at /usr/sbin/named

    /etc/rc.d/named correctly looks for /usr/bin/named, so I'm not wholly sure where it's getting the /usr/local/sbin path from...

    Can anyone give any clues? (Am currently reinstalling via WHM to cPanel RELEASE tree instead of STABLE, with force just in case that solves it)

    UPDATE: No, it didn't solve it.
     
    #1 HorburySchool, Jul 30, 2008
    Last edited: Jul 30, 2008
  2. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Minneapolis, MN
    The problem is likely corrupted syntax. Did you check the syntax of /etc/namedb/named.conf file? The command /scripts/rebuildnamedconf won't fix corrupted syntax, sometimes.
     
  3. HorburySchool

    HorburySchool Active Member

    Joined:
    Dec 14, 2007
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    6
    Not managed to spot anything out of the ordinary thus far... here's the entire file split across 2 posts...

    Code:
    // $FreeBSD: src/etc/namedb/named.conf,v 1.26.4.1 2008/01/13 20:48:23 dougb Exp $
    //
    // Refer to the named.conf(5) and named(8) man pages, and the documentation
    // in /usr/share/doc/bind9 for more details.
    //
    // If you are going to set up an authoritative server, make sure you
    // understand the hairy details of how DNS works.  Even with
    // simple mistakes, you can break connectivity for affected parties,
    // or cause huge amounts of useless Internet traffic.
    
    options {
    	// Relative to the chroot directory, if any
    	directory	"/etc/namedb";
    	pid-file	"/var/run/named/pid";
    	dump-file	"/var/dump/named_dump.db";
    	statistics-file	"/var/stats/named.stats";
    
    // If named is being used only as a local resolver, this is a safe default.
    // For named to be accessible to the network, comment this option, specify
    // the proper IP address, or delete this option.
    	listen-on	{ 127.0.0.1; };
    
    // If you have IPv6 enabled on this system, uncomment this option for
    // use as a local resolver.  To give access to the network, specify
    // an IPv6 address, or the keyword "any".
    //	listen-on-v6	{ ::1; };
    
    // These zones are already covered by the empty zones listed below.
    // If you remove the related empty zones below, comment these lines out.
    //	disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
    //	disable-empty-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.0.IP6.ARPA";
    //	disable-empty-zone "1.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 addition to the "forwarders" clause, you can force your name
    // server to never initiate queries of its own, but always ask its
    // forwarders only, by enabling the following line:
    //
    //	forward only;
    
    // If you've got a DNS server around at your upstream provider, enter
    // its IP address here, and enable the line below.  This will make you
    // benefit from its cache, thus reduce overall DNS traffic in the Internet.
    /*
    	forwarders {
    		127.0.0.1;
    	};
    */
    	/*
    	 * If there is a firewall between you and nameservers you want
    	 * to talk to, you might need to uncomment the query-source
    	 * directive below.  Previous versions of BIND always asked
    	 * questions using port 53, but BIND versions 8 and later
    	 * use a pseudo-random unprivileged UDP port by default.
    	 */
    	// query-source address * port 53;
    };
    
    // If you enable a local name server, don't forget to enter 127.0.0.1
    // first in your /etc/resolv.conf so this server will be queried.
    // Also, make sure to enable it in /etc/rc.conf.
    
    // The traditional root hints mechanism. Use this, OR the slave zones below.
    zone "." { type hint; file "named.root"; };
    
    /*	Slaving the following zones from the root name servers has some
    	significant advantages:
    	1. Faster local resolution for your users
    	2. No spurious traffic will be sent from your network to the roots
    	3. Greater resilience to any potential root server failure/DDoS
    
    	On the other hand, this method requires more monitoring than the
    	hints file to be sure that an unexpected failure mode has not
    	incapacitated your server.  Name servers that are serving a lot
    	of clients will benefit more from this approach than individual
    	hosts.  Use with caution.
    
    	To use this mechanism, uncomment the entries below, and comment
    	the hint zone above.
    */
    /*
    zone "." {
    	type slave;
    	file "slave/root.slave";
    	masters {
    		192.5.5.241;	// F.ROOT-SERVERS.NET.
    	};
    	notify no;
    };
    zone "arpa" {
    	type slave;
    	file "slave/arpa.slave";
    	masters {
    		192.5.5.241;	// F.ROOT-SERVERS.NET.
    	};
    	notify no;
    };
    zone "in-addr.arpa" {
    	type slave;
    	file "slave/in-addr.arpa.slave";
    	masters {
    		192.5.5.241;	// F.ROOT-SERVERS.NET.
    	};
    	notify no;
    };
    */
    
    /*	Serving the following zones locally will prevent any queries
    	for these zones leaving your network and going to the root
    	name servers.  This has two significant advantages:
    	1. Faster local resolution for your users
    	2. No spurious traffic will be sent from your network to the roots
    */
    // RFC 1912
    zone "localhost"	{ type master; file "master/localhost-forward.db"; };
    zone "127.in-addr.arpa" { type master; file "master/localhost-reverse.db"; };
    zone "255.in-addr.arpa"	{ type master; file "master/empty.db"; };
    
    // RFC 1912-style zone for IPv6 localhost address
    zone "0.ip6.arpa"	{ type master; file "master/localhost-reverse.db"; };
    
    // "This" Network (RFCs 1912 and 3330)
    zone "0.in-addr.arpa"		{ type master; file "master/empty.db"; };
    
    // Private Use Networks (RFC 1918)
    zone "10.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "16.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "17.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "18.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "19.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "20.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "21.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "22.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "23.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "24.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "25.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "26.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "27.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "28.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "29.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "30.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "31.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "168.192.in-addr.arpa"	{ type master; file "master/empty.db"; };
    
    // Link-local/APIPA (RFCs 3330 and 3927)
    zone "254.169.in-addr.arpa"	{ type master; file "master/empty.db"; };
    
    // TEST-NET for Documentation (RFC 3330)
    zone "2.0.192.in-addr.arpa"	{ type master; file "master/empty.db"; };
    
    // Router Benchmark Testing (RFC 3330)
    zone "18.198.in-addr.arpa"	{ type master; file "master/empty.db"; };
    zone "19.198.in-addr.arpa"	{ type master; file "master/empty.db"; };
    
    // IANA Reserved - Old Class E Space
    zone "240.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "241.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "242.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "243.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "244.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "245.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "246.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "247.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "248.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "249.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "250.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "251.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "252.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "253.in-addr.arpa"		{ type master; file "master/empty.db"; };
    zone "254.in-addr.arpa"		{ type master; file "master/empty.db"; };
    
     
  4. HorburySchool

    HorburySchool Active Member

    Joined:
    Dec 14, 2007
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    6
    Code:
    // IPv6 Unassigned Addresses (RFC 4291)
    zone "1.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "3.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "4.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "5.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "6.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "7.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "8.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "9.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "a.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "b.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "c.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "d.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "e.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "0.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "1.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "2.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "3.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "4.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "5.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "6.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "7.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "8.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "9.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "a.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "b.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "0.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "1.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "2.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "3.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "4.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "5.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "6.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "7.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    
    // IPv6 ULA (RFC 4193)
    zone "c.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "d.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    
    // IPv6 Link Local (RFC 4291)
    zone "8.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "9.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "a.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "b.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    
    // IPv6 Deprecated Site-Local Addresses (RFC 3879)
    zone "c.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "d.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "e.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    zone "f.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
    
    // IP6.INT is Deprecated (RFC 4159)
    zone "ip6.int"			{ type master; file "master/empty.db"; };
    
    // NB: Do not use the IP addresses below, they are faked, and only
    // serve demonstration/documentation purposes!
    //
    // Example slave zone config entries.  It can be convenient to become
    // a slave at least for the zone your own domain is in.  Ask
    // your network administrator for the IP address of the responsible
    // master name server.
    //
    // Do not forget to include the reverse lookup zone!
    // This is named after the first bytes of the IP address, in reverse
    // order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6.
    //
    // Before starting to set up a master zone, make sure you fully
    // understand how DNS and BIND work.  There are sometimes
    // non-obvious pitfalls.  Setting up a slave zone is usually simpler.
    //
    // NB: Don't blindly enable the examples below. :-)  Use actual names
    // and addresses instead.
    
    zone "bigsis.horbury.wakefield.sch.uk" {
        type master;
        file "/etc/namedb/bigsis.horbury.wakefield.sch.uk.db";
    };
    
    zone "horbury.wakefield.sch.uk" {
        type master;
        file "/etc/namedb/horbury.wakefield.sch.uk.db";
    };
    
     
Loading...

Share This Page