still having trouble with bind9 server

[Clark Martin]

On Dec 14, 2010, at 10:44 AM, Scott B. wrote:

> -- 
> Scott Berry
> MCP and A Plus Certified
> 
> Hi there,
> 
> I am still having trouble with the bind9 server.  The last person
> trying to help me I didn't understand his/her comments.  So I am
> sending this again.
> 
> Here are the files I think are the culprits:
> 
> root at pilotalk:/etc/bind# tail -f /var/log/syslog
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.options:14: unknown option '12.109.229.75'
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.options:15: unknown option '12.109.229.87'
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.default-zones:2: unknown option 'zone'
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.default-zones:10: unknown option 'zone'
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.default-zones:15: unknown option 'zone'
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.default-zones:20: unknown option 'zone'
> Dec 14 12:32:46 pilotalk named[10097]:
> /etc/bind/named.conf.default-zones:25: unknown option 'zone'
> Dec 14 12:32:46 pilotalk named[10097]: /etc/bind/named.conf:12: '}'
> expected near end of file
> Dec 14 12:32:46 pilotalk named[10097]: loading configuration: unexpected token
> Dec 14 12:32:46 pilotalk named[10097]: exiting (due to fatal error)
> 
> 
> Beginning of Named.conf.options:
> options {
>        directory "/var/cache/bind";
> 
>        // If there is a firewall between you and nameservers you want
>        // to talk to, you may need to fix the firewall to allow multiple
>        // ports to talk.  See http://www.kb.cert.org/vuls/id/800113
> 
>        // If your ISP provided one or more IP addresses for stable
>        // nameservers, you probably want to use them as forwarders.
>        // Uncomment the following block, and insert the addresses replacing
>        // the all-0's placeholder.
> 
>        // forwarders {
>                12.109.229.75;
> 12.109.229.87;
> // };

You have the command and terminator commented out, it should be

>  forwarders {
> 	12.109.229.75;
> 	12.109.229.87;
>  };

> 
>        auth-nxdomain no;    # conform to RFC1035
>        listen-on-v6 { any; };
> End Of Named.conf.options
> 
> 
> Beginning of Named.conf.local:
>  //
> // Do any local configuration here
> //
> 
> // Consider adding the 1918 zones here, if they are not used in your
> // organization
> //include "/etc/bind/zones.rfc1918";
> 
> 
> # This is the zone definition. replace example.com with your domain name
> 
> zone "pilotalk.net" {
> type master;
> file "/etc/bind/zones/pilotalk.net.db";
> };
> 
> # This is the zone definition for reverse DNS. replace 0.168.192 with your netw$
> 
> zone "0.1.168.192.in-addr.arpa" {
>     GNU nano 2.2.4            File: named.conf.local
> 

This is missing the terminator "};", and the second line doesn't make sense

> 
> zone "pilotalk.net" {
> type master;
> file "/etc/bind/zones/pilotalk.net.db";
> };
> 
> # This is the zone definition for reverse DNS. replace 0.168.192 with your netw$
> 
> zone "0.1.168.192.in-addr.arpa" {
> type master;
> file "/etc/bind/zones/rev.0.1.168.192.in-addr.arpa";

My comments aren't comprehensive, I don't know BIND that well.

You might consider installing Webmin, it provides a convenient GUI front end to BIND and several other servers.  The errors I noted are based on comparing your file with my named.conf generated by Webmin.