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.
Okay, where to begin. I'm coming pretty close to just going on and buying a book. Probably will anyways as this is part of my new job.
We are trying to have two dns servers. The Master works fine and does what it is supposed to do. Here is its named.conf file.
-----------------------------------------------------------
# Use with the following in named.conf, adjusting the allow list as needed:
key "rndckey" {
algorithm hmac-md5;
secret "xxxxxxxxxxxxxxxxxxxxx";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndckey"; };
};
# End of named.conf
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
query-source address * port 53;
};
zone "." {
type hint;
file "named.ca";
};
zone "xxxxxxxxxxxxxxxx" {
type master;
file "xxxxxxxxxxxxxx.com.dns";
};
zone "xxxxxxxxxxxxxx" {
type master;
file "xxxxxxxxxxxxxx.com.dns";
};
zone "xxxxxxxxxxxxxx" {
type master;
file "xxxxxxxxxxxxxx.com.dns";
};
#zone "xxxxxxxxxxxxxx." {
# type master;
# file "xxxxxxxxxxxxxx.com.dns";
#};
#zone "xxxxxxxxxxxxxx." {
# type master;
# file "xxxxxxxxxxxxxx.com.dns";
#};
zone "xxxxxxxxxxxxxx" {
type master;
file "xxxxxxxxxxxxxx.com.dns";
};
zone "xxxxxxxxxxxxxx" {
type master;
file "xxxxxxxxxxxxxx.com.dns";
};
logging {
category lame-servers { null; };
};
55,0-1 Bot
---------------------------------------------------------
I didn't set that one up, it was here before I started.
We are trying to set up anohter server to act as slave and to replicate the data on its own. Below is its named.conf file.
---------------------------------------------------------
# Use with the following in named.conf, adjusting the allow list as needed:
key "rndckey" {
algorithm hmac-md5;
secret "xxxxxxxxxxxxxxxxx";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndckey"; };
};
# End of named.conf
};
zone "xxxxxxxxxxxxxx.com" {
type slave;
file "/var/named/chroot/var/named/slaves/xxxxxxxxxxxxxx.com.dns";
masters {66.77.99.5;};
};
zone "xxxxxxxxxxxxxx.com" {
type slave;
file "/var/named/chroot/var/named/slaves/xxxxxxxxxxxxxx.com.dns";
masters {66.77.99.5;};
};
zone "xxxxxxxxxxxxxx.com" {
type slave;
file "/var/named/chroot/var/named/slaves/xxxxxxxxxxxxxx.com.dns";
masters {66.77.99.5;};
};
zone "xxxxxxxxxxxxxx" {
type slave;
file "/var/named/chroot/var/named/slaves/xxxxxxxxxxxxxx.arpa.dns";
};
zone "xxxxxxxxxxxxxx {
type slave;
file "/var/named/chroot/var/named/slaves/xxxxxxxxxxxxxx";
masters {xxxxxxxxxxxxxx};
};
----------------------------------------------------------
i go to check to see if the files were replicated, there's nothing there. i check the /var/log/messages file/ and i get messges saying file cant be found. ill post that soon. i just want to take out my company's information first. any ideas why this isnt working properly? btw, named is chrooted
Just an FYI: If the named process is started in a chroot environment (-t /var/named/chroot), then there is no need to specify the full path for the slave files.
Since you already have the directory specified in the options section (directory /var/named), then all slave file locations can be specifed relative to the <chroot>/<directory> base. i.e.
relative to: /var/named/chroot/var/named
Code:
Master DNS Server named.conf
// Load the external view mydomain.com zone
zone "mydomain.com" in {
type master; // Zone is a master
notify yes; // Send notifies?
allow-query { any; }; // Allow anyone to query zone
file "data/db.mydomain"; // Load zone file
};
Slave DNS Server named.conf
// Load the external view mydomain.com zone
zone "mydomain.com" in {
type slave; // Zone is a slave
masters { 206.124.x.x; }; // IP of master zone server
allow-query { any; }; // Allow anyone to query zone
file "slaves/db.mydomain"; // Store slave zone file as...
};
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.