Hi list,
I have a test environment with 3 VMs running different versions of BIND -
9.7.3-P3, 9.8.1-P1 and 9.9.0rc1. On all 3 machines "rndc status" reports
unrealistic "number of zones:". For example, when the zones configured at
named.conf are 3, the number reported is "number of zones: 18" and w
On 01/03/12 03:40, Beavis wrote:
Just want to piggy back on this topic is there any documentation
available online that shows a deployment guideline for Anycast?
There's not much to it:
1. Create the anycast IP on your servers
2. Route the anycast IP to your servers
3. Make bind listen on t
On 01/03/2012 11:20, Emil Natan wrote:
> Do any of you experience the same issue? Any ideas what I'm missing or
> what's wrong?
Automatic empty zones?
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
On Thu, Mar 1, 2012 at 1:26 PM, Matthew Seaman <
m.sea...@infracaninophile.co.uk> wrote:
> On 01/03/2012 11:20, Emil Natan wrote:
> > Do any of you experience the same issue? Any ideas what I'm missing or
> > what's wrong?
>
> Automatic empty zones?
>
>
Thanks for the input. It seems you are right
I think you want to use
options {
empty-zones-enable no;
};
in your named.conf configuration file to disable all empty zones.
Look at the DNS and BIND reference from Cricket Liu
ciao!
Banana
On Mar 1, 2012, at 1:10 PM, Emil Natan wrote:
>
>
> On Thu, Mar 1, 2012 at 1:26 PM,
On 01/03/2012 12:10, Emil Natan wrote:
> On Thu, Mar 1, 2012 at 1:26 PM, Matthew Seaman <
> m.sea...@infracaninophile.co.uk> wrote:
>
>> > On 01/03/2012 11:20, Emil Natan wrote:
>>> > > Do any of you experience the same issue? Any ideas what I'm missing or
>>> > > what's wrong?
>> >
>> > Automatic
It's really more elegant way to disable the empty zones, Thanks.
On Thu, Mar 1, 2012 at 2:14 PM, Flex Banana wrote:
> I think you want to use
>
> options {
> empty-zones-enable no;
> };
>
> in your named.conf configuration file to disable all empty zones.
>
> Look at the DNS and BIND reference f
Built in root hints zones with class IN.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubsc
On Thu, Mar 1, 2012 at 2:27 PM, Matthew Seaman <
m.sea...@infracaninophile.co.uk> wrote:
> On 01/03/2012 12:10, Emil Natan wrote:
> > On Thu, Mar 1, 2012 at 1:26 PM, Matthew Seaman <
> > m.sea...@infracaninophile.co.uk> wrote:
> >
> >> > On 01/03/2012 11:20, Emil Natan wrote:
> >>> > > Do any of y
Spain, Dr. Jeffry A. wrote:
> Which of these alternative empty zones should be used in the current DNS
> environment and why?
In my named.conf I have set up empty zones for the whole of 240/4. I view
RFC 6303 as the minimum necessary for a hygienic name server, but there
are a number of other pe
That should be it. And that's probably why adding and removing the custom
root.hints file does not change the count, when enabled it's the one
counted and when disabled, the build in one is counted. Thanks.
ena
On Thu, Mar 1, 2012 at 2:41 PM, Mark Andrews wrote:
>
> Built in root hints zones wi
On 29/02/12 03:55, ju wusuo wrote:
Have seen some anycast DNS implementations using more than one address,
some times even on the same subnet, any considerations or reasons for
doing that?
We do that.
We use two different, indepentent methods to route traffic to the IPs.
We feel this provides
> > Have seen some anycast DNS implementations using more than one address,
> > some times even on the same subnet, any considerations or reasons for
> > doing that?
>
> We do that.
>
> We use two different, indepentent methods to route traffic to the IPs.
> We feel this provides a greater degre
In article ,
sth...@nethelp.no wrote:
> > > Have seen some anycast DNS implementations using more than one address,
> > > some times even on the same subnet, any considerations or reasons for
> > > doing that?
> >
> > We do that.
> >
> > We use two different, indepentent methods to route traffi
>> Just for clarification, do I understand correctly that if none of the
>> empty zones described in RFC 6303 are set up explicitly in the bind
>> 9.9.0 configuration file, then bind 9.9.0 will process them as such
>> anyway using built-in generic zone processing rules?
> Yes. To expand a bit
> In my named.conf I have set up empty zones for the whole of 240/4. I view RFC
> 6303 as the minimum necessary for a hygienic name server, but there are a
> number of other permanent bogon address ranges which it makes sense to stub
> out locally.
Would you please elaborate on how you are mana
On Mar 1 2012, Spain, Dr. Jeffry A. wrote:
[...]
Also I see that bind 9.9.0 uses built-in root hints if those are not
explicitly configured.
That has been true since BIND 9.2.
If the root hints are updated on ftp://rs.internic.net/domain/, would it
require a new build of bind to incorporate
In article ,
Chris Thompson wrote:
> On Mar 1 2012, Spain, Dr. Jeffry A. wrote:
>
> [...]
> >Also I see that bind 9.9.0 uses built-in root hints if those are not
> >explicitly configured.
>
> That has been true since BIND 9.2.
>
> >If the root hints are updated on ftp://rs.internic.net/domain
18 matches
Mail list logo
