Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration.
Master:
zone "example.com" { type master; notify no; allow-query { any; }; file "db.example"; };
Slave:
zone "example.com" { type slave; masters { master-server-ip; }; notify no; allow-query { any; }; file "db.example"; };
I also have the allow-transfer statement added to the master server with the ip address of the slave server.
Thanks,
Dan
Am Di, den 28.09.2004 schrieb Dan Righter um 23:57:
Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration.
Dan
I guess you are running bind chrooted, so be sure the slave zones are located under /var/named/chroot/var/named/slaves/.
file "slaves/db.example";
Alexander
P.S. Please send plain text mails only to this list. No html formatted mails. Thanks.
HTML HTML HTML How about that ALEX!!!!!
-----Original Message----- From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com] On Behalf Of Alexander Dalloz Sent: Tuesday, September 28, 2004 4:20 PM To: For users of Fedora Core releases Subject: Re: Slave DNS Server
Am Di, den 28.09.2004 schrieb Dan Righter um 23:57:
Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration.
Dan
I guess you are running bind chrooted, so be sure the slave zones are located under /var/named/chroot/var/named/slaves/.
file "slaves/db.example";
Alexander
P.S. Please send plain text mails only to this list. No html formatted mails. Thanks.
-- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp Serendipity 00:18:07 up 8 days, 2:22, load average: 5.13, 4.64, 4.59
The master needs to be set to "notify yes;" if you want the slave to automagically pull the updated zone.
On Tue, 28 Sep 2004, Dan Righter wrote:
Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration.
Master:
zone "example.com" { type master; notify no; allow-query { any; }; file "db.example"; };
Slave:
zone "example.com" { type slave; masters { master-server-ip; }; notify no; allow-query { any; }; file "db.example"; };
I also have the allow-transfer statement added to the master server with the ip address of the slave server.
Thanks,
Dan
Dan Righter wrote:
Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration.
Master:
zone "example.com" { type master; notify no; allow-query { any; }; file "db.example"; };
Slave:
zone "example.com" { type slave; masters { /master-server-ip; };/ notify no; allow-query { any; }; file "db.example"; };
I also have the allow-transfer statement added to the master server with the ip address of the slave server.
Thanks,
Dan
...also make sure that you have your rndc key working.
This is probably basic, but can you clue me in on what the rndc key is for and how to check if it is working?
Thanks,
Dan ----- Original Message ----- From: "Patrick Nelson" pnelson@neatech.com To: "For users of Fedora Core releases" fedora-list@redhat.com Sent: Tuesday, September 28, 2004 10:34 PM Subject: Re: Slave DNS Server
Dan Righter wrote:
Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration.
Master:
zone "example.com" { type master; notify no; allow-query { any; }; file "db.example"; };
Slave:
zone "example.com" { type slave; masters { /master-server-ip; };/ notify no; allow-query { any; }; file "db.example"; };
I also have the allow-transfer statement added to the master server with the ip address of the slave server.
Thanks,
Dan
...also make sure that you have your rndc key working.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Dan Righter wrote:
This is probably basic, but can you clue me in on what the rndc key is for and how to check if it is working?
rndc is a tool for runtime control of the nameserver. /etc/rndc.key is the file containing a security key to ensure that only the right people can use it. The bind rpm post-install script should create this file for you, and your main named.conf file should include it like this:
include "/etc/rndc.key";
It is, however, nothing to do with slave servers.
The tool you need to diagnose this problem is "dig", which is part of the "bind-utils" package.
On your slave server, run "dig @master-server-ip example.com axfr"
This should output a list of the zone example.com. If it doesn't, the reason is that the master is not configured to allow transfers to the slave.
If you get a connection failure then you may have firewall problems.
If the transfer works, the problem lies with the slave server configuration.
That should narrow the problem down a bit.
Paul.
Thanks, I narrowed the problem down to a missing folder on the slave server. Core 2 seems a bit different compared to the older versions of Red Hat.
--Dan
----- Original Message ----- From: "Paul Howarth" paul@city-fan.org To: "For users of Fedora Core releases" fedora-list@redhat.com Sent: Wednesday, September 29, 2004 10:21 AM Subject: Re: Slave DNS Server
Dan Righter wrote:
This is probably basic, but can you clue me in on what the rndc key is
for
and how to check if it is working?
rndc is a tool for runtime control of the nameserver. /etc/rndc.key is the file containing a security key to ensure that only the right people can
use
it. The bind rpm post-install script should create this file for you, and
your
main named.conf file should include it like this:
include "/etc/rndc.key";
It is, however, nothing to do with slave servers.
The tool you need to diagnose this problem is "dig", which is part of the "bind-utils" package.
On your slave server, run "dig @master-server-ip example.com axfr"
This should output a list of the zone example.com. If it doesn't, the
reason
is that the master is not configured to allow transfers to the slave.
If you get a connection failure then you may have firewall problems.
If the transfer works, the problem lies with the slave server
configuration.
That should narrow the problem down a bit.
Paul.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Am Mi, den 29.09.2004 schrieb Dan Righter um 16:41:
Thanks, I narrowed the problem down to a missing folder on the slave server. Core 2 seems a bit different compared to the older versions of Red Hat.
--Dan
No, it is not. You just have to respect the case bind is used in chrooted mode. But I directed you against this in my yesterday's reply. The slaves directory with proper permissions is created automatically during RPM install.
Alexander
On Tuesday 28 September 2004 23:57, Dan Righter wrote:
Does anyone know how to setup a slave DNS server on Fedora Core 2? I've configured the master server and the slave, but I'm getting a permission denied error in the logs when the slave tries to update. Below is an example of my configuration. Master: zone "example.com" { type slave; notify no; allow-query { any; }; file "db.example"; }; Slave:
zone "example.com" {
type slave;
masters { master-server-ip; };
notify no;
allow-query { any; };
file "db.example";
};
It should look like this:
/etc/resolve.conf search your_domain.com nameserver 192.168.2.your_ip
/etc/hosts 127.0.0.1 localhost.localdomain localhost
append your /etc/sysconfig/network-scripts/ifcfg-eth0 with PEERDNS=no
The your /etc/named.conf zone "example.com" { type slave; masters { 192.168.2.1; }; file "slave-forward_zone_file"; };
zone "2.168.192.IN-ADDR.ARPA" { type slave; masters { 192.168.2.1; }; file "slave-reverse_zone_file"; };
restart named service examin the slave-forward_zone_file zone and the slave-reverse_zone_file they should contain copies of the master from your master server. Dont forget to replace the IPs for your own. Cheers ;->