Hi Bert,
I tried to compile your recursor pdns-recursor-3.1.5-snapshot.tar.bz2 with
the PROFILEFLAG option and ended up with errors. I can't reproduce them
right now. Are there any significance differences between
pdns-recursor-3.1.5-snapshot.tar.bz2 and the latest release?
One more question, can
On Feb 7, 2008 5:00 AM, Hugo van der Kooij <[EMAIL PROTECTED]> wrote:
> What is the big deal with all the addresses and such? Why not run a
> single instance for all domains? I wouldn't even dare to guess the rate
> of domains per nameserver on a global scale. Why can't you do so as well?
What I'm
Thanks for the feedback - looks like I'll have to have another go at
multiple instances :)
The idea is to keep all .com.au domains on a .com.au name server.
Domain: domain.com.au
Nameservers: ns40.dns.com.au, ns41.dns.com.au, ns42.dns.com.au, ns43.dns.com.au
Domain: domain.com
Nameservers: ns10.
Hi everybody,
We are heading up to a release of version 3.1.5 of the PowerDNS Recursor.
Since it has been a long time since 3.1.4, which appears to have been a very
good release, we are doing some snapshots.
This snapshot 3 is in production, and appears to work, but take care when
deploying!
Ava
On Wednesday 06 February 2008 21:14:29 Eugene Pefti wrote:
> Has anybody tried to migrate from Microsoft DNS to PDNS.
> As far as I understand zone2sql utility could be used but it requires
> named.conf to be around with the entry pointing to the zone file. Is there
> any tool or script available t
Has anybody tried to migrate from Microsoft DNS to PDNS.
As far as I understand zone2sql utility could be used but it requires
named.conf to be around with the entry pointing to the zone file. Is there
any tool or script available to do that? I have about 500 domains to
migrate.
Eugene
__
That was fast, thanks Bert!
Actually I wanted to fill the content of TXT record with an entry to handle
SPF but somehow it slipped my mind.
Eugene
-Original Message-
From: bert hubert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 06, 2008 11:52 AM
To: Eugene Pefti
Cc: pdns-users@m
On Wed, Feb 06, 2008 at 11:40:38AM -0800, Eugene Pefti wrote:
> Hi friends,
>
> Can anybody explain me the meaning of this fatal error:
> [TEST coherence between SOA and ANY records]: server failure (IN/ANY:
> premiere1.com.)
> [TEST coherence between NS and ANY records]: server failure (IN/ANY:
>
Hi friends,
Can anybody explain me the meaning of this fatal error:
[TEST coherence between SOA and ANY records]: server failure (IN/ANY:
premiere1.com.)
[TEST coherence between NS and ANY records]: server failure (IN/ANY:
premiere1.com.)
[TEST coherence between MX and ANY records]: server failure
On Wed, Feb 06, 2008 at 07:00:36PM +0100, Hugo van der Kooij wrote:
> I though pdns was about simplicity. This is making things complex
> without any benefit but with the added burden of IP adresses and such to
> maintain.
>
> It isn't wrong but it seems illogical to me to make things this comple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicholas Orr wrote:
| I want to run the following.
|
| Host 1 - USA
| eth0:0 = 192.168.0.1 = ns10.dns.com
| eth0:1 = 192.168.0.2 = ns20.dns.net
| eth0:2 = 192.168.0.3 = ns30.dns.info
| eth0:3 = 192.168.0.4 = ns40.dns.com.au
|
| Host 2 - AU
| eth0:0 =
On Wed, Feb 06, 2008 at 10:56:55PM +1100, Nicholas Orr wrote:
> I want to run the following.
Nicholas,
The best way to do this is to run multiple copies of PowerDNS
simultaneously. PowerDNS has easy support for this using the 'virtual'
configuration feature.
See http://doc.powerdns.com/virtual.h
I want to run the following.
Host 1 - USA
eth0:0 = 192.168.0.1 = ns10.dns.com
eth0:1 = 192.168.0.2 = ns20.dns.net
eth0:2 = 192.168.0.3 = ns30.dns.info
eth0:3 = 192.168.0.4 = ns40.dns.com.au
Host 2 - AU
eth0:0 = 192.168.1.1 = ns11.dns.com
eth0:1 = 192.168.1.2 = ns21.dns.net
eth0:2 = 192.168.1.3 =
13 matches
Mail list logo
