Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

named.conf syntax

Status
Not open for further replies.

bubarooni

Technical User
May 13, 2001
506
US
since the search function is down...

i have set up a fc4 box and installed the zimbra collaboration suite on it.

i can receive email from the outside world on but i can't get it delivered to the mailboxes. the mail sits in the deferred queue.

from what i've read i need to setup split dns on the machine because it sits behind a pix firewall. in order to do so i need to edit the named.conf file. i've followed the wiki to the best of my ability.

no matter how i edit the named.conf it always returns errors. i've checked it in vi for unwanted characters and it's clean. i feel i must be making some kind of syntax error but am also baffled by the 'command not found' statements when i try to start named.

i have spent days in the zimbra forums with no resolution.

Code:
options {
       directory "/var/named";
       dump-file "/var/named/data/cache_dump.db";
       statistics-file "/var/named/data/named_stats.txt";
forwarders { 12.127.16.68 ; 24.217.0.5 ; };
};
include "/etc/rndc.key";
// We are the master server for zmail.wbhcp.net
zone "zmail.wbhcp.net" {
    type master;
    file "/var/named/data/db.zmail.wbhcp.net";
};


Code:
[root@zmail /]# service named start
/etc/init.d/named: line 1: options: command not found
/etc/init.d/named: line 2: directory: command not found
/etc/init.d/named: line 3: dump-file: command not found
/etc/init.d/named: line 4: statistics-file: command not found
/etc/init.d/named: line 5: syntax error near unexpected token `}'
/etc/init.d/named: line 5: `forwarders { 12.127.16.68 ; 24.217.0.5 ; };'


thanks in advance for any ideas or pointers.
 
Although I see a number of sections potentially missing from your named.conf file, the first thing I'd ask is whether you've checked /etc/init.d/named (called by "service named start") to check if you are in fact parsing the named.conf you expect.

Similarly, if your /etc/init.d/named is expecting a chroot jail for your named configuration files, its possible that you do not have your named.conf in the right place.

Additionally (whew) you might not have appropriate privs for the user defined in /etc/init.d/named to read the named.conf you've written (presumably in the right place).

Check, in general, to assure that your specific named.conf can actually be found and read. The implication from the errors you've shown is that there is almost nothing found by named when it starts up.



D.E.R. Management - IT Project Management Consulting
 
It looks to me like the /etc/init.d/named script has been overwritten by a copy of named.conf somehow?

Annihilannic.
 
annihilannic:

BINGO!

that is exactly what had happened.

just how does one make 'symbolic links' between files?
 
Think of it like a copy command... or else if you're like me you keep getting the parameters the wrong way around.

[tt]ln -s source dest[/tt]

Will create a symbolic link dest -> source.

Annihilannic.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top