On 10/05/07, bert hubert <[EMAIL PROTECTED]> wrote:
On Thu, May 10, 2007 at 02:22:42PM +1000, Amos Shapira wrote:
> 1. A Geo backend which will pick a CNAME record based on the IP from
which
> the query came.
> 2. A database backend (MySQL/PostgresSQL) which will resolve the name
that
> the CNAM
On Tue, May 08, 2007 at 07:33:50PM +0200, thomas polnik wrote:
> I must prevent, that customer B can do a zone transfer for
> customer-a.de. If I use
> allow-axfr-ips=192.168.100.10, 10.10.10.10
> customer B can take a look in all data from the domain customer-a.de.
Indeed - this is not currently
On Fri, May 04, 2007 at 03:44:27PM +0200, Juergen Georgi wrote:
> four valid NS records expire after 12 hours. The fifth
> (delphi.bsz-bw.de) expires after one day. This is bad,
> because the recursor uses incomplete delegation data half
> of the time. Then you see only one NS RR:
Juergen,
This
On Thu, May 10, 2007 at 02:22:42PM +1000, Amos Shapira wrote:
> 1. A Geo backend which will pick a CNAME record based on the IP from which
> the query came.
> 2. A database backend (MySQL/PostgresSQL) which will resolve the name that
> the CNAME points to into an IP address.
>
> I wonder if that I
On Wed, May 09, 2007 at 12:52:15PM +0200, Andre Lorbach wrote:
> It has done a great job so far. However recently a problem occurred when
> our master dns server was updated. Since this update, our master dns
> server is sending so called glue records along with dns zone transfers.
Updated to what
Hello,
I am tasked with proposing a way to load-balance requests over a global
network of servers and though that PowerDNS looks like just the tool for
this, but I've never used it before and wonder whether my expectations and
plan are real.
What I was thinking about is to have two "layers"
1.
Hi all,
After building custom Debian-packages with some source patches, I kind
of found out what the cause of my problems is.
Remember that one of my slave nameservers reported:
> Apr 23 13:37:07 callisto pdns[2433]: Received NOTIFY for assen.nl from
> 87.251.57.140 for which we are not authorita
Hello all,
We are successfully using powerdns since some years as secondary name
server on a Debian Server, Version 2.9.17 .
It has done a great job so far. However recently a problem occurred when
our master dns server was updated. Since this update, our master dns
server is sending so called
