0.099 rows=407 loops=1)
Index Cond: ((domain_id = 1) AND (ordername IS NOT NULL))
Planning time: 0.194 ms
Execution time: 0.575 ms
(13 rows)
Time: 1.320 ms
So I'd expect pg to be significantly faster for you.
-JimC
--
James Cloos
ws in records and replace
them with columns in the domains table for each of the components of an soa.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/ma
rouble - there is at least one open
PD> bug related to unknown record syntax
PD> (https://github.com/PowerDNS/pdns/issues/804)
Thanks.
It is kind of anoying that the sql backend needs the \# and decimal
lenght. It should be able to calculate the length itself, and require
only the hex-encoded d
Looking at the code, I take it that TYPEnnn should work, but how should
the content be formatted?
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman
s occur, but
is there a record format I can use for a row which contributes to the
max(change_date) calculation w/o being queriable via dns? AKA, not
part of an axfr?
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
___
Pdns-users mailing
it accomplishes the task.
Doing so is also useful to determine how to rectify w/o calling pdnssec.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
What differences does pdnssec show-zone reveal between the master and
the slaves?
Is there anything in the cryptokeys tables which differ?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users
r the secondaries -- and with the
trigger properly in place -- works well.
It also helps that nsd allocates *much* less vmem than power does (3×64M
vs 1.2G) which makes it more viable for small, extremely affordable vps's.
-JimC
--
James Cloos OpenPGP: 1024
://dnssec-debugger.verisignlabs.com/${ZONE} and
http://dnsviz.net/d/${ZONE}/dnssec/ were complaining about
verification until I switched back to axfr.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.p
3, 14, 15 on the other two.
Otherwise the data is identical.
I presume that the unsynced .id is enough to confuse verifiers?
Is there a reasonable way out of this short of moving the axfr'ed zone
off of these servers, to make replication easy?
-JimC
--
James Cloos OpenPGP: 1024
>>>>> "PvD" == Peter van Dijk writes:
PvD> A change to domain_id calls for rectify on the '"receiving" zone. A
PvD> change to name or type calls for rectify on the zone that the
PvD> (unchanged) domain_id points to.
Thanks for the details!
-JimC
those which
support the conecept) so that rectify and the like can be triggered
from w/in SQL. The NOTIFY payload can specify what to run and on
which zones.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users
play in slaving
decisions.
Doesn't the slave re-create sigs?
There was a post to that effect sometime in the last month or so.
Or did I misunderstand that discussion?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-user
When using axfr slaving, how much lack of tod sync can pdns tolerate?
Centiseconds? Deciseconds? Seconds? Dekaseconds? Hectoseconds?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
>>>>> "bh" == bert hubert writes:
bh> the launch of http://blog.powerdns.com
Added to gwene as gwene.com.powerdns.blog
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-use
>>>>> "JM" == Jan-Piet Mens writes:
JM> It's the rdata [from] running dnssec-keygen ...
OK. Thanks!
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdn
>>>>> "JM" == Jan-Piet Mens writes:
JM> It's just the Base64-encoded blob, e.g.:
'the blob' doesn't answer my question.
Is it just random bits or the result of running hmac-md5 on something?
-JimC
Should the tsigkeys.secret column have any structure?
Or is it just base64-encoded random bits?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman
rectify. Not
every time, but every so often.)
I've spent some time looking into a set of functions (I use pgsql) for
making changes, which can do all of the necessary logic when adding,
removing or changing an RR, but I haven't yet compiled a full list of
what exactly is required for
eck their
documentation as to what IPs you have to enable for AXFR.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
>>>>> "iic" == ivan i@vvpgroup com writes:
iic> | 31 | mydomain.com | NULL | NULL | NATIVE |NULL |
NULL|
Change that NATIVE to MASTER to permit AXFR mirroring to your
secondaries.
-JimC
--
James Cloos
value 86376 in that answer is the record's TTL.
If you were to dig one of the records which you want to cache and post
the answer section, you should answer his question.
I hope that this helps.
-JimC
--
James Cloos OpenPGP: 1024D/ED7
AS> addresses of all servers. (verified with tcpdump)
As a side note, pdns in MASTER mode does the same thing when it sends
out notifies. It even sends notif(y|ies) to its own address(es),
which it then rejects.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
the column default adjusted, of course, for non-postgres.)
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
ROM domains;
(which I grabbed from some old notes; obviously domains.serial needs to
be replaced with GREATEST and a join).
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
iability of the data store and improve
the UIs used for storing or manipulating the data.
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns
query should be smaller than 17 octets,
and that only happens when querying RRs of the root zone. Ie, doing a
dig . NS or a dig . SOA or similar.
If it was not due to packet corruption, perhaps it is a probe. Such as
a UPD ping or traceroute. Or maybe someone ran nmap
ect * from records where type='NAPTR' limit 2;
or so?
I'd followed the examples from the manual, but NAPTR consumers never
liked the resulting on-wire data, and as I said the server leaked like
a gusher.
Thanks,
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP:
debs.)
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
I thought I had read that the gpgsql backend now supports auto serial
numbers, but I cannot get it to work.
Did I misread, or am I screwing up the config?
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
___
Pdns-users m
30 matches
Mail list logo