Current time: 11-16-2024, 06:41 AM Hello There, Guest! (LoginRegister)


Post Reply 
problem with bind
Author Message
nuke3d Offline
Junior Member
*

Posts: 107
Joined: Sep 2007
Reputation: 1
Post: #10
RE: problem with bind
I don't really use it at the moment, so they are pretty empty. The logs don't contain anything helpful.

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";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only
//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/keys.conf";
include "/etc/bind/named.conf.local";

named.conf.options
Code:
options {
    directory "/var/cache/bind";

    // 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 8.1 and later use an unprivileged
    // port by default.

    // query-source address * port 53;

    // 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 {
    //  0.0.0.0;
    // };

    recursion no;
    transfer-format many-answers; //this is for speed up the transfer to a secondary dns

    auth-nxdomain no;    # conform to RFC1035
    listen-on-v6 { any; };
};
04-16-2009 12:39 AM
Find all posts by this user Quote this message in a reply
Post Reply 


Messages In This Thread
problem with bind - leha - 03-31-2009, 12:02 AM
RE: problem with bind - joximu - 03-31-2009, 12:18 AM
RE: problem with bind - leha - 03-31-2009, 12:27 AM
RE: problem with bind - leha - 04-01-2009, 06:15 PM
RE: problem with bind - joximu - 04-01-2009, 06:43 PM
RE: problem with bind - Illidan - 04-15-2009, 10:14 AM
RE: problem with bind - Milligan - 04-15-2009, 06:57 PM
RE: problem with bind - nuke3d - 04-15-2009, 07:05 PM
RE: problem with bind - Illidan - 04-15-2009, 09:36 PM
RE: problem with bind - nuke3d - 04-16-2009 12:39 AM
RE: problem with bind - Milligan - 04-17-2009, 12:02 AM

Forum Jump:


User(s) browsing this thread: 4 Guest(s)