On 3/9/12 7:58 AM, "Romgo" wrote:
> Even if I use a VIP I can reproduce the issue :
> If the first VIP (so the nameserver 1) is down, I'll have the same
> drawbacks. As the resolver will timeout before falling back to the second
> nameserver.
Sure, we don't live in a perfect world. You can estab
Hello,
I know that I can use VIP with any software (corosync, Linux HA...) But
this will not explain the origin of the issue I am facing :)
Even if I use a VIP I can reproduce the issue :
If the first VIP (so the nameserver 1) is down, I'll have the same
drawbacks. As the resolver will timeout b
On 03/08/2012 06:26 PM, michoski wrote:
Meant to add one thing... In our configuration, we actually have two
recursive VIPs per site, and even considered three (internal IPs are cheap).
We do this.
We also make the two different VIPs use different underlying tech - one
is an anycast route a
In article ,
michoski wrote:
> On 3/8/12 8:15 AM, "Romgo" wrote:
> > I can use a VIP for DNS server, but I though that master/slave
> > configuration was made in order to avoid to use a VIP.
>
> Master/slave was to avoid SPOF -- if the master dies, who cares with a
> reasonable expire time. :
On 3/8/12 10:20 AM, "Mike Hoskins" wrote:
> On 3/8/12 8:15 AM, "Romgo" wrote:
>> I can use a VIP for DNS server, but I though that master/slave
>> configuration was made in order to avoid to use a VIP.
>
> Master/slave was to avoid SPOF -- if the master dies, who cares with a
> reasonable expir
On 3/8/12 8:15 AM, "Romgo" wrote:
> I can use a VIP for DNS server, but I though that master/slave
> configuration was made in order to avoid to use a VIP.
Master/slave was to avoid SPOF -- if the master dies, who cares with a
reasonable expire time. :-)
So go ahead, setup a VIP...even using fr
Hello,
thanks for the answer. That was my first change :
/etc/resolv.conf like :
domain example.fr
search example.fr example2.fr
nameserver 192.168.0.1
nameserver 192.168.0.2
options rotate
options timeout:1
options attempts:1
This works fine.
But the issue is now mainly coming from the client
On 8 Mar 2012, at 02:58, Lyle Giese wrote (on bind-users):
> On linux boxes, adding
>
> options rotate
>
> to the /etc/resolv.conf helps.
[cross-posted, reply-to header set]
Is there a DHCP option which expresses that, and which
typical fielded DHCP clients will respe
On linux boxes, adding
options rotate
to the /etc/resolv.conf helps.
Lyle Giese
LCR Computer Services, Inc.
On 03/07/12 06:54, Bostjan Skufca wrote:
Problem is, most of client resolvers (not resolving nameservers, but
resolvers on workstations etc) query first specified nameserver first,
the
On 3/7/12 9:15 AM, "Barry Margolin" wrote:
> In article ,
> ro...@free.fr wrote:
>> I use bind on my network as DNS Server. Running bind
>> 1:9.6.ESV.R4+dfsg-0+lenny4
>> on Debian Lenny.
>>
>> The setup is quite usual : one master server with one slave server.
>>
>> The slave sync the zone from
In article ,
ro...@free.fr wrote:
> Dear community,
>
> I use bind on my network as DNS Server. Running bind
> 1:9.6.ESV.R4+dfsg-0+lenny4
> on Debian Lenny.
>
> The setup is quite usual : one master server with one slave server.
>
> The slave sync the zone from the master.
>
> I discover tha
Problem is, most of client resolvers (not resolving nameservers, but
resolvers on workstations etc) query first specified nameserver first, then
after timeout start with the others. You should create a HA IP for such
uses.
b.
On 7 March 2012 10:23, wrote:
> Dear community,
>
> I use bind on my
On Sat, May 1, 2010 at 11:32 AM, Sajeev Ramakrishnan
wrote:
> I have a question regarding configuration of DNSSEC. If I intend to sign a
> particular zone which has master and a slave, would I have to sign both?
No.
Assuming you've correctly setup zone xfers from master to slave, the
actual zone
13 matches
Mail list logo
