> On 12 Aug 2008, at 23:12:18, Mark Andrews wrote:
>
> >
> >>> Is this an artifact of the -P2 changes or was the use of RTT dropped
> >>> for some other reason?
> >>
> >> You didn't say which version you were running.
>
>
> Our NMS systems tend to be running BIND 9.3.5-P1. The -P2 rollout is
On 12 Aug 2008, at 23:12:18, Mark Andrews wrote:
>
>>> Is this an artifact of the -P2 changes or was the use of RTT dropped
>>> for some other reason?
>>
>> You didn't say which version you were running.
Our NMS systems tend to be running BIND 9.3.5-P1. The -P2 rollout is
in progress. There
> > Is this an artifact of the -P2 changes or was the use of RTT dropped
> > for some other reason?
>
> You didn't say which version you were running.
>
> I'd be quite surprised if this were an artifact of the -P1 and -P2
> changes. I'd be less surprised if it were a bug introduced in 9.5.0.
> My understanding is that the RTT-based forwarder selection is "banded",
> so that if a bunch of forwarders' RTTs all fall within the same "band"
> they'll be used either randomly, or in a strict round-robin fashion.
As I understand it that was a feature of BIND8, not BIND9.
(It'll be coming b
> Is this an artifact of the -P2 changes or was the use of RTT dropped
> for some other reason?
You didn't say which version you were running.
I'd be quite surprised if this were an artifact of the -P1 and -P2
changes. I'd be less surprised if it were a bug introduced in 9.5.0.
--
Evan Hunt -
On 12 Aug 2008, at 19:46:37, Kevin Darcy wrote:
> Merton Campbell Crockett wrote:
>> My corporate network consists of roughly 100 different sites located
>> throughout North America. At each site there is a Network Management
>> System (NMS) running ISC BIND and DHCP. Each NMS is the master nam
Merton Campbell Crockett wrote:
> My corporate network consists of roughly 100 different sites located
> throughout North America. At each site there is a Network Management
> System (NMS) running ISC BIND and DHCP. Each NMS is the master name
> server for the forward and reverse DNS zones
My corporate network consists of roughly 100 different sites located
throughout North America. At each site there is a Network Management
System (NMS) running ISC BIND and DHCP. Each NMS is the master name
server for the forward and reverse DNS zones assigned to the site.
No NMS has direct
