Hi Nikolaos,
> b) Network connection to the whole data center dies, or the whole
> data center loses power or otherwise dies. There's really no other
> choice to failover that than DNS, unless you manage to route the
> same IP address to two different data centers and just update t
that your O/S doesn't choose a link-local or other address for the
query.
FYI, you definitely can not use :: for local-address in the config of either
service. Otherwise, the daemon may not reply to IPv6 queries using the same
address it received them on.
FYI!
===
tive to get outgoing IPv6 to
work. This instructs the recursor what address to bind to for this.
Good luck!
Darren Gamble
Senior Systems Architect
Core Service Development
Shaw Communications
3636 - 23 Street NE
Calgary, Alberta, Canada
T2E 8Z5
(403) 781-4948
o/pdns-user
the recursor handle a nameserver name with both A and
record types? Is it capable of using both if one is unreachable? Is
there a preference?
Thanks!
Darren Gamble
Systems Architect
Core Service Development
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary
> Can pdns-recursor be set to forward queries with recursive bit set ?
It doesn't, sorry.
I've previously opened up ticket #199 to request this functionality on a
per-zone basis. This is blocking replacing some of our DNS servers with
PowerDNS.
====
like powerdns to use the rd bit, and
also situations where we don't.
I think the best way to handle this would be two different configuration
directives to handle the two different situations.
====
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesy
is
would interfere with package managers' naming conventions.
========
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
___
Pdns-users
omeone on the list at least try to reproduce the problem.
====
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
___
Pdns-users mailing list
Pd
ers to re-get the NS
records for the domain.
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
___
Pdns-users mailing list
Pdns-users@mailman.power
is definitely a blocking issue for us.
Please let us know if we can provide any more information or help.
Thanks!
========
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
airs.
If there's some specific reason why you'd like inter-cache peering, let
us know what it is, and we could probably suggest an appropriate
solution for you.
Good luck!
====
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue
runs well on
less. You'll just have to lower that cache size
>From our experience, at least, I think you can put your mind at ease.
:-)
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403)
also logged by
default by most distributions into the messages file.
As well, many users log "Warning-and-higher" into an "action item" log
file, which the stats wouldn't belong in.
Just FYI!
D
entage
of us, at least) that the broken secondary server stops being
authoritative rather than provide out-of-date information.
If the user doesn't like this behavior, they have the option to
configure the expiry time to a very large value.
Darren Gamble
Systems
r in front of the
servers, or software on both web servers to manage a VIP. But, this is just
the most common solution, not the only one.
FYI,
========
Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
lly sure yet what exact situation(s) still
cause the recursor to do this. I know Bert has previously squashed at
least two bugs on this very subject.
In theory, the recursor should always remove all old information for an
RRset when new information for that RRset is cached.
===
he new set. This appears to be causing this
problem. So yes, it does unfortunately still look like a problem with
the recursor.
Note also that a DNS server can not (is not supposed to, by RFC) return
and/or keep a rrset where any of the TTLs differ. This is because,
well, it can cause exactly th
2.9.21 snapshot at least),
This zone, and many others like it, should resolve properly if you
upgrade all of your caches to at least 3.1.2. That is what you need to
do. 3.1.3 should be released soon too, which contains some important
crash fixes too.
Darren Gamble
Plann
l bet that if you were to query the 2.X
server for the NS records for this zone when it is broken, you will see
a single, broken NS record that is not present on the 3.1.2 server at
all.
More recent pdns versions have lots of other useful fixes, too.
FYI,
Darren G
cases. The NS records on each server
will reveal the problem.
Hope this helps,
====
Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
_
20 matches
Mail list logo
