On Wed, Dec 12, 2012 at 6:04 AM, Tony Finch wrote:
> Mark Andrews wrote:
>>
>> You need to wait for named to stop
>>
>> p=`rndc stop -p | awk '{print $2}'`
>> while kill -0 $p
>> do
>> sleep 1
>> done
>> /etc/rc.d/rc.named start
This looks like FreeBSD. If so, just use 'service named rest
Hi,
I m planning to add cname records to two A records to different IPs
provided by two ISP. Can I loadbalance traffic then?
Like say i need to play with mail services and I have 2 ISPs.say ISP A and
ISP B.
MX 10 mail.example.com 20.20.20.20 (from isp A)
Mx 20 mail01.example.com 30.30.30.30 (f
于 2012-12-13 18:06, Sten Carlsen 写道:
> Well, you can NOT use an ACL in any form of notify.
>
> This topic has been discussed a number of times, look in the archives.
>
that's right. thanks.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-
Well, you can NOT use an ACL in any form of notify.
This topic has been discussed a number of times, look in the archives.
BTW: I would think programming a solution from e.g. a database would be
easy.
On 13/12/12 10:43, Feng He wrote:
> This would be easy by hand, but not by programming, since I
This would be easy by hand, but not by programming, since I have lots of
zones for updates :)
于 2012-12-13 17:35, Sten Carlsen 写道:
> also-notify { 74.81.81.82; 74.81.81.81; };
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubsc
On 13/12/12 10:09, Feng He wrote:
> Thanks.
>
> So how to handle the case described as below?
>
> We already have the also-notify{} section in the global options{} block.
>
> But for a special zone, just want to include another IP to also-notify
> besides the global IPs.
>
>
>
>
> 于 2012-12-13 17:
Thanks.
So how to handle the case described as below?
We already have the also-notify{} section in the global options{} block.
But for a special zone, just want to include another IP to also-notify
besides the global IPs.
于 2012-12-13 17:00, Sten Carlsen 写道:
>
> On 13/12/12 9:46, Feng He w
On 13/12/12 9:46, Feng He wrote:
> Hello Mark,
>
> My named.conf looks as:
>
> acl "NAMESVR" { 74.81.81.82; };
NAMESVR is an acl, it could look like {74.81.0.0/16} or {any}
Essentially it is a kind of bitmask, not a list of IPs.
>
> options {
> directory "/var/cache/bind";
> recursion
Hello Mark,
My named.conf looks as:
acl "NAMESVR" { 74.81.81.82; };
options {
directory "/var/cache/bind";
recursion no;
version "unknown";
allow-transfer { NAMESVR; };
also-notify { NAMESVR; };
allow-update { 127.0.0.1; };
};
# zone begins
zone "test.com" {
9 matches
Mail list logo