LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
LinkBack Search this Thread
Old 06-29-2009, 02:49 PM   #1
5pike
LQ Newbie
 
Registered: Dec 2005
Distribution: Gentoo
Posts: 6

Rep: Reputation: 0
BIND DNS name servers


Hi,

I trying to setup two name servers, a primary and a secondary. I have two machines, each with gentoo and bind installed. However I am unable to get them working and I don't know why. Could someone please take a look at my config files and give me some idea what could be wrong?

/var/bind/pri/db.127.0.0

$TTL 1h
0.0.127.in-addr.arpa. IN SOA ns1.pikedom.com. hostmaster.pikedom.com. (
3 ; Serial
3h ; Refresh after 3 hours
1h ; Retry after 1 hour
1w ; Expire after 1 week
1h ) ; Negative caching TTL of 1 hour

0.0.127.in-addr.arpa. IN NS ns1.pikedom.com.
0.0.127.in-addr.arpa. IN NS ns2.pikedom.com.

1.0.0.127.in-addr.arpa. IN PTR localhost.


/var/bind/pri/db.78.86.197

$TTL 1h
197.86.78.in-addr.arpa. IN SOA ns1.pikedom.com. hostmaster.pikedom.com. (
3 ; Serial
3h ; Refresh after 3 hours
1h ; Retry after 1 hour
1w ; Expire after 1 week
1h ) ; Negative caching TTL of 1 hour

;
; Name servers
;
197.86.78.in-addr.arpa. IN NS ns1.pikedom.com.
197.86.78.in-addr.arpa. IN NS ns2.pikedom.com.

;
; Addresses pointing to canonical name
;
253.197.86.78.in-addr.arpa. IN PTR ns1.pikedom.com.


/var/bind/pri/db.78.86.198

$TTL 1h
198.86.78.in-addr.arpa. IN SOA ns1.pikedom.com. hostmaster.pikedom.com. (
3 ; Serial
3h ; Refresh after 3 hours
1h ; Retry after 1 hour
1w ; Expire after 1 week
1h ) ; Negative caching TTL of 1 hour

;
; Name servers
;
198.86.78.in-addr.arpa. IN NS ns1.pikedom.com.
198.86.78.in-addr.arpa. IN NS ns2.pikedom.com.

;
; Addresses pointing to canonical name
;
1.198.86.78.in-addr.arpa. IN PTR ns2.pikedom.com.


/var/bind/pri/db.78.86.202

$TTL 1h
202.86.78.in-addr.arpa. IN SOA ns1.pikedom.com. hostmaster.pikedom.com. (
3 ; Serial
3h ; Refresh after 3 hours
1h ; Retry after 1 hour
1w ; Expire after 1 week
1h ) ; Negative caching TTL of 1 hour

;
; Name servers
;
202.86.78.in-addr.arpa. IN NS ns1.pikedom.com.
202.86.78.in-addr.arpa. IN NS ns2.pikedom.com.

;
; Addresses pointing to canonical name
;
76.202.86.78.in-addr.arpa. IN PTR brocas.pikedom.com.



/var/bind/pri/db.pikedom.com

$TTL 1h
pikedom.com. IN SOA ns1.pikedom.com. hostmaster.pikedom.com. (
4 ; Serial
3h ; Refresh after 3 hours
1h ; Retry after 1 hour
1w ; Expire after 1 week
1h ) ; Negative caching TTL of 1 hour

;
; Name servers
;
pikedom.com. IN NS ns1.pikedom.com.
pikedom.com. IN NS ns2.pikedom.com.

;
; IP Addresses for the canonical names.
;
localhost.pikedom.com. IN A 127.0.0.1
brocas.pikedom.com. IN A 78.86.202.76
ns1.pikedom.com. IN A 78.86.197.253
ns2.pikedom.com. IN A 78.86.198.1

;
; Aliases
;
tongue.pikedom.com. IN CNAME ns1.pikedom.com.
harper.pikedom.com. IN CNAME ns2.pikedom.com.


/etc/bind/named.conf

options {
directory "/var/bind";
pid-file "/var/run/named/named.pid";
version "not currently available";
recursion no;
allow-transfer{78.86.198.1;};
allow-query{any;};
};

logging {

channel default_file { file "/var/log/bind/default.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel general_file { file "/var/log/bind/general.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel database_file { file "/var/log/bind/database.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel security_file { file "/var/log/bind/security.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel config_file { file "/var/log/bind/config.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel resolver_file { file "/var/log/bind/resolver.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel xfer-in_file { file "/var/log/bind/xfer-in.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel xfer-out_file { file "/var/log/bind/xfer-out.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel notify_file { file "/var/log/bind/notify.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel client_file { file "/var/log/bind/client.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel unmatched_file { file "/var/log/bind/unmatched.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel queries_file { file "/var/log/bind/queries.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel network_file { file "/var/log/bind/network.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel update_file { file "/var/log/bind/update.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel dispatch_file { file "/var/log/bind/dispatch.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel dnssec_file { file "/var/log/bind/dnssec.log" versions 3 size 5m; severity dynamic; print-time yes; };
channel lame-servers_file { file "/var/log/bind/lame-servers.log" versions 3 size 5m; severity dynamic; print-time yes; };

category default { default_file; };
category general { general_file; };
category database { database_file; };
category security { security_file; };
category config { config_file; };
category resolver { resolver_file; };
category xfer-in { xfer-in_file; };
category xfer-out { xfer-out_file; };
category notify { notify_file; };
category client { client_file; };
category unmatched { unmatched_file; };
category queries { queries_file; };
category network { network_file; };
category update { update_file; };
category dispatch { dispatch_file; };
category dnssec { dnssec_file; };
category lame-servers { lame-servers_file; };

};


zone "pikedom.com" in {
type master;
file "pri/db.pikedom.com";
allow-update{none;};
allow-transfer{78.86.198.1;};
};

zone "197.86.78.in-addr.arpa" in {
type master;
file "pri/db.78.86.197";
allow-transfer{78.86.198.1;};
};

zone "198.86.78.in-addr.arpa" in {
type master;
file "pri/db.78.86.198";
allow-transfer{78.86.198.1;};
};

zone "202.86.78.in-addr.arpa" in {
type master;
file "pri/db.78.86.202";
allow-transfer{78.86.198.1;};
};

zone "0.0.127.in-addr.arpa" in {
type master;
file "pri/db.127.0.0";
allow-update{none;};
};

// Disabled as caching is not required.
//zone "." in {
// type hint;
// file "root.cache";
//};



Thanks very much for all help received.
 
Old 06-29-2009, 04:46 PM   #2
rweaver
Senior Member
 
Registered: Dec 2008
Location: Louisville, OH
Distribution: Debian, CentOS, Slackware, RHEL, Gentoo
Posts: 1,833

Rep: Reputation: 163Reputation: 163
I took a quick look, but what is the exact error you're getting? Have you checked selinux and verified you don't have iptables rules blocking the dns? Some information from the logs during startup would be useful.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to set DNS servers? How to stop auto change of DNS servers? newtovanilla Linux - Newbie 1 10-29-2008 09:19 PM
How to get Windows Clients to be served DNS from a Linux BIND-DNS Server texmansru47 Linux - Networking 12 07-10-2008 07:06 PM
LXer: DNS: The Bind Leading the Bind LXer Syndicated Linux News 0 06-15-2006 10:33 PM
BIND doesn't resolve hostnames information for which is stored on other DNS servers GD_19 Linux - Networking 5 01-03-2006 08:31 PM
Microsoft ISA Firewall Returns Port Scan Warnings From Linux BIND DNS Servers. ramram29 Linux - Security 4 01-26-2004 10:09 PM


All times are GMT -5. The time now is 06:26 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration