Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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;};
};
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.