On Mon, 2006-07-03 at 18:01 -0600, Charles Curley wrote:
> I seem to be having a problem with zone transfer.
>
> I have bind running inside my local domain (an experimental network
> that the outside world never sees).
>
> I set up the master as follows:
>
>
> // We are authoritative for this zone.
> zone "localdomain" IN {
> type master;
> file "localdomain";
> allow-transfer {
> # 192.168.1.12;
> 192.168.1.32;
> 192.168.1.4;
> };
> allow-update { none; };
> };
>
> For the same zone, the slave is as follows:
>
>
> // We are authoritative for this zone.
> zone "localdomain" IN {
> type slave;
> file "localdomain";
> masters { 192.168.1.3; };
> };
>
> The transfer appears to start. The master reports, e.g:
>
> Jul 3 17:46:14 charlesc named[27334]: client 192.168.1.4#48326: transfer of 'localdomain/IN': AXFR started
>
> It never reports that the transfer ends.
>
> Jul 3 17:46:16 dragon named[14083]: zone localdomain/IN: Transfer started.
> Jul 3 17:46:16 dragon named[14083]: transfer of 'localdomain/IN' from 192.168.1.3#53: connected using 192.168.1.4#48326
> Jul 3 17:46:16 dragon named[14083]: dumping master file: tmp-EYbYqUHud2: open: permission denied
> Jul 3 17:46:16 dragon named[14083]: transfer of 'localdomain/IN' from 192.168.1.3#53: failed while receiving responses: permission denied
> Jul 3 17:46:16 dragon named[14083]: transfer of 'localdomain/IN' from 192.168.1.3#53: end of transfer
>
> What am I doing wrong?
----
This - among other entries works for me...
*** master ***
zone "example.com" {
type master;
file "/var/named/example.com.hosts";
allow-update {
mainoffice;
};
also-notify {
192.168.1.7;
};
};
zone "3.168.192.in-addr.arpa" {
type master;
file "/var/named/192.168.1.rev";
allow-update {
mainoffice;
};
also-notify {
192.168.1.7;
};
};
*** slave ***
zone "example.com" {
type slave;
masters {
192.168.1.5;
};
file "/var/named/slaves/example.com.hosts";
};
zone "3.168.192.in-addr.arpa" {
type slave;
masters {
192.168.1.5;
};
file "/var/named/slaves/192.168.1.rev";
};
Craig
