Mental Patient on Mon, 4 Aug 2003 11:08:05 -0400 |
On Mon, 2003-08-04 at 10:36, kaze wrote: > gh-systems.com.zone above is from the slave, ns2, but it is the identical > file from the master ns1 as it got here by ftp. Remove the ftp'd files and restart named. If they dont transfer, thats a big problem. Did you configure the other 2 nameservers as clients of the primary? Something like: zone "domain" { type slave; masters { IP_ADDRESS_OF_AUTHORITATIVE_MASTER; }; file "filename_to_write_cached_file_to"; allow-transfer { DIRECTIVES; }; } And in your master you'd have something along the lines of zone "domain" { type master; file "filename_of_zone"; allow-transfer { DIRECTIVES; }; } If that crap is setup properly then all you should need to do is edit the zone on the master, change records, incremenent serialnumber and kill -HUP the master only. When it (the master) restarts, it should notify the secondary servers listed in the SOA of the zones it's serving. The secondarys should transfer the zones and write them to their cache. When debugging cache issues, know who you're running as. Often linux distributions run named as root, so cache permissions aren't much of an issue. If you're chrooting or running as an unprivleged user, be aware of this and make sure the cache files can be manipulated as the user bind runs as. Grab the bind tarball. Theres lots of examples in there. -- Mental (Mental@NeverLight.com) CARPE NOCTEM, QUAM MINIMUM CREDULA POSTERO. GPG public key: http://www.neverlight.com/pas/Mental.asc Attachment:
signature.asc
|
|