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
Ah, I see now, dunno, sorry for the noise :)
b.
On 16 January 2012 16:41, Phil Mayers wrote:
> On 16/01/12 15:19, Bostjan Skufca wrote:
>
>> IP in parenthesis: It is the destination IP to which the client has sent
>> his query.
>>
>
> No, not that item. That
IP in parenthesis: It is the destination IP to which the client has sent
his query.
For example: Useful if you are switching IPs around in your DHCP and you
want to make sure all clients have updated their configurations.
b.
On 16 January 2012 15:19, Phil Mayers wrote:
> On 16/01/12 14:13, Ch
Hi everyone,
is binding to all interfaces at once already supported in bind9? I know
named binds to each at-the-moment-available IP address but in HA
environment with virtual interfaces a "rndc reload" is necessary for named
to pick up a new interface, which leaves a bit of a window of unavailable
Hello everyone!
I would like to ask you if anyone can point me to some more information
about configuring BIND to delegate a whole "artificial" top level domain to
another nameserver.
This far it has been a classical configuration, recursive nameserver for
local clients behind the NAT. Now I woul
5 matches
Mail list logo
