|
|
 |  |
Re: Zone transfers failFrom: Men & Mice Support Date: Friday, July 2, 2004
Time: 4:17:07 pmAt 4:02 PM -0700 7/2/04, Scott Haneda wrote:
>on 07/02/2004 12:34 PM, Men & Mice Support at cbuxton@menandmice.com wrote:
>
>> Yes. You can set this either in /var/named/conf/options, globally for
>> the server, or in /var/named/conf/zoneopt/zone.name.opt, for each
>> zone individually. Add the following to either the 'options'
>> statement block or the 'zone' statement block:
>>
>> transfer-source { 64.84.37.14; };
>>
>> Be sure to edit the file with root privileges (either by becoming
>> root or by using 'sudo'), and be sure to tell the server to reload
>> the zone. For BIND 9 on Mac OS X, you can perform this latter step
>> with this command:
>>
>> sudo rndc reload zone.name
>
>If I edit /var/named/conf/options how do I reload since there is no specific
>zone.name to reload?
Sorry about that.
sudo rndc reconfig
Then have it reload or refresh all affected zones.
>Also, I just had to slave 20 domains, it was a pain, select the NS server,
>go to menu to add slave, paste in zone name, paste in IP, click OK, select
>the NS server again, repeat, is there some faster way I can do this?
Not in the general case. AppleScript is available, of course.
If you have a DNS Management license (tier 2), you can use the
command line interface. This allows you to type all parameters into a
command at a special command prompt, which can be faster than using
the mouse in QuickDNS Manager.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
|

Return to Digital Point Solutions' Home Page |