Hi,
For our provisioning system I need to know the DNSKEY of a zone quickly
after the zone has been created (ideally the DS...). When assigning a
key to a domain (in the DB backend), it takes a few seconds before
PowerDNS actually serves the DNSKEY. What is the maximum delay for the
DNSKEY to
Hi Peter,
I just tried to ignore this issue as you said it shouldt cause any problems.
But when I edited my zone and put it back in the database (with in the SOA the
2 dots that are added by zone2sql) I get this:
:~$ host -t SOA domain.tld ip-of-the-ns-server
;; Got bad packet: extra input
Hello Frank,
putting double dots in the database certainly is not okay. When I said you
could try to ignore it, I meant single dots.
I have to ask - why are you repeatedly exporting and importing zones?
Also, PowerDNS 3.2 and 3.3 will not send these broken packets (they will send
SERVFAIL
Hi Peter,
I use this script to add complete subnets (/24s) with reverse and forward DNS.
We have 1 (main) domain and multiple services for customers, for every service
(i.e. ftth , dsl , colo etc) I add new reverse and forward DNS for this (main)
domain. This is done by a script using
Hello Frank,
I would suggest changing the script to talk to SQL directly.
Kind regards,
--
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/
On Aug 20, 2013, at 9:49 , Frank van den Diepstraten wrote:
Hi Peter,
I use this script to add complete subnets (/24s)
Hi!
I wonder how PDNS behaves when it should sign a zone which is already
pre-signed (e.g. my customer sends me a pre-signed zone although it
should send me an unsigned zone).
Of course I could just test the behavior, but I want to know if there is
a strict policy in PDNS for this scenario
On Mon, Aug 19, 2013 at 5:27 PM, Klaus Darilion
klaus.mailingli...@pernau.at wrote:
That even ignores the serial and always transfers the zone. Put in into a
loop as suggested by Tom and replace MASTER with SLAVE.
Hi Klaus,
Thanks, I've used the script suggested by Tom and it's working
Hi,
Is there a command option for pdns_control or pdnssec that
artificially bumps the zone serial in a native zone setup,
e.g. to test proper notification an replication behaviour?
Should trigger the same action that is launched when a zone
is resigned.
Kind regards,
Sebastian
--
Sebastian
Hello Sebastian,
On Aug 20, 2013, at 14:22 , Posner, Sebastian wrote:
Is there a command option for pdns_control or pdnssec that
artificially bumps the zone serial in a native zone setup,
e.g. to test proper notification an replication behaviour?
Should trigger the same action that is
Hello,
I just tested my DNS Rekursor and realized, that I have to ask a certain
address twice so that the third time the result is delivered out of the
cache. Is there a special reason for that behavior?
*** second try
Hello Gerald,
On Aug 20, 2013, at 19:30 , Gerald wrote:
I just tested my DNS Rekursor and realized, that I have to ask a certain
address twice so that the third time the result is delivered out of the
cache. Is there a special reason for that behavior?
By default, the recursor runs with
Hello Peter,
you are right. That was the problem.
Many Thanks
Gerald
On 2013-08-20 19:49, Peter van Dijk wrote:
Hello Gerald,
On Aug 20, 2013, at 19:30 , Gerald wrote:
I just tested my DNS Rekursor and realized, that I have to ask a certain
address twice so that the third time the result
Thank guys. I finally got it working on pdns v3.3. For the curious, here's
the perl script that works:
#!/usr/bin/perl
use warnings;
use strict;
$|=1; # no buffering
my $line=;
chomp($line);
unless($line eq HELO\t1) {
print FAIL\n;
print
I've put the script here guys: https://github.com/TvL2386/pdns-tools
On 08/20/2013 11:54 AM, Mohamed Brahimi wrote:
On Mon, Aug 19, 2013 at 5:27 PM, Klaus Darilion
klaus.mailingli...@pernau.at mailto:klaus.mailingli...@pernau.at
wrote:
That even ignores the serial and always transfers
14 matches
Mail list logo
