Enrico van Goor wrote:
> > > Aug 25 13:22:44 Unable to find backend willing to host example.org for
> > > potential supermaster 10.12.3.50
>
> > > The IP of the nameserver isn't is the NS records of the domain and
> > > isn't meant to. When I do add the NS record, the AXFR does work.
> > The supe
On Thu, 2011-08-25 at 15:10 +0200, Ton van Rosmalen wrote:
> Hi Enrico,
>
> Op 25-8-2011 14:08, Enrico van Goor schreef:
> > Hi All,
> >
> > I'm currently testing a setup powerdns authoritative server 3.0 and
> > anycast. There is 1 supermaster en a few superslaves. The supermaster
> > sends a
Hi Enrico,
Op 25-8-2011 14:08, Enrico van Goor schreef:
> Hi All,
>
> I'm currently testing a setup powerdns authoritative server 3.0 and
> anycast. There is 1 supermaster en a few superslaves. The supermaster
> sends an also-notify to the superslaves.
>
> The superslave does receive the NOTIFY, b
Hi All,
I'm currently testing a setup powerdns authoritative server 3.0 and
anycast. There is 1 supermaster en a few superslaves. The supermaster
sends an also-notify to the superslaves.
The superslave does receive the NOTIFY, but doesn't do an AXFR.
Aug 25 13:22:44 Received NOTIFY for example.o
Is it just me or option 'webserver=no' has no effect at all in latest
stable authoritative version ?I am running multiple vhost instances and
the port 8081 keeps conflicting.
Running pdns_server --webserver=no also is of no use!
I can confirm that. But as a workaround this config statement prev
