Hi.
I read your link about publishing real FQDNs an IPs, however I'm very
reluctant to this ... I explain ... I'm not the super pro (as you noticed
already) in this subject and I don't really know about the full range of
potential consequences. I see already now some AXFR attempts from IPs from
I have pdns 3.4.7, and recursor 3.7.3
recursor.conf is:
local-address=127.0.0.1
local-port=5300
log-common-errors=yes
quiet=yes
setgid=pdns
setuid=pdns
trace=off
pdns.conf:
daemon=yes
guardian=yes
include-dir=/etc/powerdns/pdns.d
launch=
local-address=0.0.0.0
setgid=pdns
On 18/05/2016 11:41, @lbertosolorzano wrote:
in the company are very strict
confidentiality of the data and the data Protection Act so I find it
impossible to extract real data.
If you can keep trimming down your config to a point where it still
fails, but contains no confidential data, that
On 18/05/2016 11:20, Pieter Lexis wrote:
Yes you could, pdnsutil just talks to the database. What features from pdnsutil
do you need that are not in the 3.4.9's pdnssec? If you create a ticket on
github[1] about these, we might backport these functions.
I just like the CLI for creating zones
Hi Brian,
On Wed, 18 May 2016 10:53:27 +0100
Brian Candler wrote:
> Supplementary question: could I take pdnsutil out of 4.0.0 and run it
> with 3.4.9 ? Does it only talk to the database and do nothing else?
Yes you could, pdnsutil just talks to the database. What
On 17/05/2016 10:41, Pieter Lexis wrote:
>2. Has there been any mysql schema change between 3.4.8 and 4.0.0? That
>is, can I just point 3.4.8 at the schema which I already installed?
Yes, 4.0.0 will use prepared statements instead of string expansion for
queries. Your specific issue is fixed
Alberto,
I spent 5 minutes copy pasting and setting up directories getting this to
work. You also did not supply the other included files like .options, .local
and .default-zones, so perhaps there is a problem in there I can't see.
Please understand that if you want free help from a free
*Hi Bert,
***/This are the congituration files, they're on production from 4 years
ago with bind9 without problems and the named-checkconf and
named-checkzone works correctly.
(For confidentiality, names w//ent replaced and cut 4 zones of 450)/*
root@powerdns:/etc/bind# cat named.conf
*// This
On Wed, May 18, 2016 at 10:51:58AM +0200, @lbertosolorzano wrote:
> Hi,
>
> At work are thinking to migrate our nsX servers to PowerDNS from bind,
> all its ok, but when we went to use zone2sql show this error:
Hi Alberto,
Can you make an exact set of files that fails? So an named.conf & the
Hello Dharmesh,
I have updated the compliance page. Thank you for letting us know.
Kind regards,
--
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/
On 18 May 2016, at 10:41, Dharmesh wrote:
Hello Peter,
Yes RFC3755 was obsoleted by 4033/4034/4035 but as per the details
given on
Hello Peter,
Yes RFC3755 was obsoleted by 4033/4034/4035 but as per the details given on
https://www.powerdns.com/compliance.html this page, RFC4033 is not in the
compliance list of PDNS. Since RFC4033,34,35 together makes a family of
RPC's so what exactly is not compliant in RFC 4033 or is it
Hello Chris,
On 13 May 2016, at 15:23, Chris Fokkenrood wrote:
At the moment we are running a test with powerdns v3, but cannot get
this
version to behave the way we want it to.
The idea is to overwrite some subdomains of our (dns is externally
hosted)
own domain to local server
Hello Dharmesh,
On 10 May 2016, at 11:07, Dharmesh wrote:
Also DDNS and DNSSEC is fully supported in PDNS 4.x but i am not able
to
get the details of Legacy Resolver Compatibility for Delegation Signer
(DS)
support via documentation. Is the same supported by PDNS 4.x
RFC3755 was obsoleted
13 matches
Mail list logo