LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 10-30-2009, 10:30 PM   #1
gimpy530
Member
 
Registered: Oct 2007
Posts: 98

Rep: Reputation: 16
BIND9, problem with options file


So I am setting up BIND9 for the first time by following a guide, and it is not working. I am able to resolve internal addresses, but not external. What am I doing wrong?

I used this guide:
http://ubuntuforums.org/showthread.php?t=236093

Along with information from:
https://help.ubuntu.com/community/BIND9ServerHowto

The command "named-checkzone" shows "OK" for both my zones.

Here is my options file:
Code:
File: named.conf.options                                                                                                                  

options {
        directory "/var/cache/bind";

version "get lost";
allow-transfer {"none";};
allow-recursion {192.168.1.0/24;};
};

logging{
  channel example_log{
   file "/var/log/bind.log" versions 3 size 2m;
   severity info;
   print-severity yes;
   print-time yes;
   print-category yes;
 };
 category default{
  example_log;
 };
};

forwarders {
        208.67.222.222;
        208.67.220.220;

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
};
syslog shows:
Code:
Oct 30 15:04:06 ubuntu-ampache named[27852]: connection refused resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 192.228.79.201#53
Oct 30 15:04:07 ubuntu-ampache named[27852]: connection refused resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 192.203.230.10#53
Oct 30 15:04:07 ubuntu-ampache named[27852]: connection refused resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 193.0.14.129#53
Oct 30 15:04:08 ubuntu-ampache named[27852]: connection refused resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 192.5.5.241#53
Oct 30 15:04:09 ubuntu-ampache named[27852]: connection refused resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 128.63.2.53#53
Oct 30 15:04:10 ubuntu-ampache named[27852]: connection refused resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 202.12.27.33#53
Oct 30 15:04:11 ubuntu-ampache named[27852]: connection refused resolving 'G.ROOT-SERVERS.NET/AAAA/IN': 128.63.2.53#53
Oct 30 15:04:12 ubuntu-ampache named[27852]: connection refused resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 192.112.36.4#53
Oct 30 15:04:13 ubuntu-ampache named[27852]: connection refused resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 192.33.4.12#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: connection refused resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 192.112.36.4#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: network unreachable resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: network unreachable resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: network unreachable resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: network unreachable resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: network unreachable resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
Oct 30 15:04:14 ubuntu-ampache named[27852]: network unreachable resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
Oct 30 15:04:15 ubuntu-ampache named[27852]: connection refused resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 198.41.0.4#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: connection refused resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 128.8.10.90#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
Oct 30 15:04:16 ubuntu-ampache named[27852]: network unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: connection refused resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 128.8.10.90#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
Oct 30 15:04:17 ubuntu-ampache named[27852]: network unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
Oct 30 15:04:18 ubuntu-ampache named[27852]: connection refused resolving 'C.ROOT-SERVERS.NET/AAAA/IN': 199.7.83.42#53
Oct 30 15:04:18 ubuntu-ampache named[27852]: network unreachable resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
Oct 30 15:04:18 ubuntu-ampache named[27852]: network unreachable resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
Oct 30 15:04:18 ubuntu-ampache named[27852]: network unreachable resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Oct 30 15:04:18 ubuntu-ampache named[27852]: network unreachable resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Oct 30 15:04:18 ubuntu-ampache named[27852]: network unreachable resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
 
Old 10-31-2009, 05:41 AM   #2
rupertwh
Member
 
Registered: Sep 2006
Location: Munich, Germany
Distribution: Debian / Ubuntu
Posts: 297

Rep: Reputation: 49
The 'forwarders' block should be *inside* the 'options' block, not after it.
 
Old 10-31-2009, 09:55 AM   #3
gimpy530
Member
 
Registered: Oct 2007
Posts: 98

Original Poster
Rep: Reputation: 16
I had to make some other changes, but I got it working. For anyone else who needs help, here are my config files:

named.conf
Code:
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
        type hint;
        file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};

include "/etc/bind/named.conf.local";
named.conf.local
Code:
//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

zone "jealwh.local" {
        type master;
        file "/etc/bind/zones/jealwh.local.db";
        };

zone "1.168.192.in-addr.arpa" {
     type master;
     file "/etc/bind/zones/rev.1.168.192.in-addr.arpa";
        };
named.conf.options
Code:
options {
        directory "/var/cache/bind";

version "get lost";
allow-transfer {"none";};
allow-recursion {192.168.1.0/24;};

#logging{
#  channel example_log{
#   file "/var/log/bind.log" versions 3 size 2m;
#   severity info;
#   print-severity yes;
#   print-time yes;
#   print-category yes;
# };
# category default{
#  example_log;
# };
#};

forwarders {
        208.67.222.222;
        208.67.220.220;
};
       auth-nxdomain no;    # conform to RFC1035
       listen-on-v6 { any; };
};
Logging is disabled right now since there is something about it that BIND 9 does not like, but I'll fix that later.

An example zone file:
Code:
@      IN      SOA     cyan.jealwh.local. none.jealwh.local. (
                                                        2006081401
                                                        28800
                                                        3600
                                                        604800
                                                        38400
 )
$TTL 1d;
      IN      NS              cyan.jealwh.local.

cyan            IN      A       192.168.1.150
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with Bind9 rytec Linux - Server 7 09-02-2009 04:26 PM
bind9 zone file question r3gan Linux - Software 6 06-18-2008 05:49 PM
shared zone file in bind9 matiasquestions Linux - Server 2 04-04-2008 09:02 AM
bind9 failed - bindnamed: chroot(): no such file or directory rly74 Linux - Software 1 05-29-2007 03:16 PM
Bind9 problem WiWa Linux - Networking 3 06-06-2004 05:27 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 10:59 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration