With a static-stub zone (new in BIND 9.8), your server would not prime its
cache with the bad NS
rrset from the authoritative server. It would simply start all query
resolution for the domain in
question (possibly bigger than the zone) at that server, thus bypassing the
bad NS rrset.
Chris,
What's the difference between a stub zone and a static-stub zone?
I have been thinking they are the same.
With a stub zone, your server would ask the server with bad NS records
for the NS record set, and would then try to resolve all queries against
the zone using that NS
On Fri, Mar 04, 2011 at 06:55:07PM -0800, Chris Buxton wrote:
...
With a static-stub zone (new in BIND 9.8), your server would not prime its
cache with the bad NS rrset from the authoritative server. It would simply
start all query resolution for the domain in question (possibly bigger than
On Fri, Mar 04, 2011 at 11:40:54PM -0800, Chris Buxton wrote:
...
A static-stub zone involves an iterative query, the potential for a referral,
and then potentially recursion to follow the referral.
Conditional forwarding (a zone of type forward) involves a recursive query.
If the answer
Haven't done it but don't see why not. Since every entry in named.conf
specifies the zone file you can definitely have multiple zones all
pointing to the same zone file. (We do that for many ancillary zones
that we want to point to our primary domain so have an aliases file that
uses the @
On 3/4/2011 11:46 AM, John Wobus wrote:
I'm going to split our authoritative servers into internal
and external views.
Is there anything I can do to try to talk you out of doing this?
AlanC
signature.asc
Description: OpenPGP digital signature
On Fri, 2011-03-04 at 11:46 -0500, John Wobus wrote:
Hi,
Can a zone file a slave in one view and the same zone file
be served by another view?
It is a bad idea, although I know (from experience) it will work for
static zones. One problem is you need to remember to reload the zone in
both
On Mar 4, 2011, at 8:46 AM, John Wobus wrote:
Hi,
Can a zone file a slave in one view and the same zone file
be served by another view?
You can do this for static master zones, but it's not a good idea for slaves.
Depending on the use case for your internal view, you may be able to solve
On 04.03.11 11:46, John Wobus wrote:
Can a zone file a slave in one view and the same zone file
be served by another view?
in fact, yes. but it apparently won't work as you'd expect.
I'm going to split our authoritative servers into internal
and external views. My question concerns zones
In message 79391b3d-6106-420b-9056-717a5e5fa...@cornell.edu, John Wobus write
s:
Hi,
Can a zone file a slave in one view and the same zone file
be served by another view?
I'm going to split our authoritative servers into internal
and external views. My question concerns zones that we
On Fri, Mar 04, 2011 at 11:46:05AM -0500, John Wobus wrote:
...
Can a zone file a slave in one view and the same zone file
be served by another view?
...
I assume you mean something like this:
view here {
match-clients { here; };
zone example.us {
type slave;
On Sat, Mar 05, 2011 at 09:36:56AM +1100, Mark Andrews wrote:
...
masters { 127.0.0.1 key external.key; };
...
Hmmm! You can do that, can't you? I tend to try to keep one key to one
IP address in a view - people get confused even so.
As I said, this still does two zone
2011/3/5 Chris Buxton chris.p.bux...@gmail.com:
On Mar 4, 2011, at 8:46 AM, John Wobus wrote:
Hi,
Can a zone file a slave in one view and the same zone file
be served by another view?
You can do this for static master zones, but it's not a good idea for slaves.
Depending on the use case
On Mar 4, 2011, at 5:42 PM, terry wrote:
2011/3/5 Chris Buxton chris.p.bux...@gmail.com:
On Mar 4, 2011, at 8:46 AM, John Wobus wrote:
Hi,
Can a zone file a slave in one view and the same zone file
be served by another view?
You can do this for static master zones, but it's not a
On Mar 4, 2011, at 11:34 PM, Joseph S D Yao wrote:
On Fri, Mar 04, 2011 at 06:55:07PM -0800, Chris Buxton wrote:
...
With a static-stub zone (new in BIND 9.8), your server would not prime its
cache with the bad NS rrset from the authoritative server. It would simply
start all query
15 matches
Mail list logo
