main freshness
Maybe there is a problem with TSIG?
> -Ursprüngliche Nachricht-
> Von: Pdns-users Im
> Auftrag von Ronny Wagner via Pdns-users
> Gesendet: Mittwoch, 13. April 2022 16:24
> An: Pdns-users@mailman.powerdns.com
> Betreff: Re: [Pdns-users] PDNS Slave - While checking domain fresh
rs Im
> Auftrag von Ronny Wagner via Pdns-users
> Gesendet: Mittwoch, 13. April 2022 11:44
> An: Pdns-users@mailman.powerdns.com
> Betreff: [Pdns-users] PDNS Slave - While checking domain freshness
>
> Debian: Buster
> Version: PowerDNS Authoritative Server 4.5.4 (C)
AA2a01:4f8:120:9041::b
;; Query time: 23 msec
;; SERVER: 178.63.70.104#53(178.63.70.104)
;; WHEN: Wed Apr 13 16:11:25 CEST 2022
;; MSG SIZE rcvd: 133
-Ursprüngliche Nachricht-
Von: Chris Wopat
Gesendet: Mittwoch, 13. April 2022 13:33
An: Ronny Wagner
Cc: Pdns-users@mailman.powerdn
On Wed, Apr 13, 2022 at 09:43:49AM +, Ronny Wagner via Pdns-users wrote:
> Debian: Buster
> Version: PowerDNS Authoritative Server 4.5.4 (C) 2001-2022 PowerDNS.COM BV
>
> Config:
> autosecondary=yes
> daemon=yes
> guardian=yes
> include-dir=/etc/powerdns/pdns.d
> launch=
> local-address=, ,
You're using MySQL replication as well as autosecondary? Seems like it
should be one or the other. Generally zones would be NATIVE if using
sql replication.
Telnetting to tcp 53 isn't a test of much of anything, you probably
should use the `dig` command, perhaps:
dig @ example.com SOA
On Wed, A
Debian: Buster
Version: PowerDNS Authoritative Server 4.5.4 (C) 2001-2022 PowerDNS.COM BV
Config:
autosecondary=yes
daemon=yes
guardian=yes
include-dir=/etc/powerdns/pdns.d
launch=
local-address=, ,
log-dns-details=yes
log-dns-queries=yes
log-timestamp=yes
query-local-address=, ,
resolver=127.0.
Hi Peter,
On 26-11-2013 15:04, Peter van Dijk wrote:
On Nov 26, 2013, at 14:56 , Ruben Laban wrote:
I just ran into the very same issue. Only in our case the (super)masters are
BIND instead of Windows Server. Everything *seems* to be working just fine, but
that big nasty warning does make fo
Hello Ruben,
On Nov 26, 2013, at 14:56 , Ruben Laban wrote:
> I just ran into the very same issue. Only in our case the (super)masters are
> BIND instead of Windows Server. Everything *seems* to be working just fine,
> but that big nasty warning does make for a nasty gut feeling. We haven't put
Hi,
On 22-5-2012 7:58, Emiel van Berlo wrote:
Hi,
We have setup a PowerDNS 3.1 server and have added a slave zone.
The master is on a windows 2008 dns.
There is some confusion with the SOA.
In PowerDNS the SOA from the slave zone has this value :
ns2.danego.net. noc.danego.net. 2010110341 28
On Tue, May 22, 2012 at 03:19:13PM +0200, Emiel van Berlo wrote:
> The manual warns about possible strange behaviour with this trailing
> dot business.
> When I do a dig to my dns servers everything seems o.k.
> But will it be o.k. in six months?
>
> When I setup a master or native domain we don't
The manual warns about possible strange behaviour with this trailing
dot business.
When I do a dig to my dns servers everything seems o.k.
But will it be o.k. in six months?
When I setup a master or native domain we don't put in the trailing
dot and we follow the manual.
(SOA : ns1.danego.net n...
On Tue, May 22, 2012 at 10:59:22AM +0200, Emiel van Berlo wrote:
> o.k. then why doesn't the slaved NS and MX records have this trailing
> dot in the powerdns database?
>
The server adds them. You do not need to add a dot "." to every record
in a database, if the software can do it. It matches a
On Tue, May 22, 2012 at 10:59:22AM +0200, Emiel van Berlo wrote:
> o.k. then why doesn't the slaved NS and MX records have this trailing
> dot in the powerdns database?
Do you have _any_ records with trailing dot in the powerdns database?
$ for server in ns1 ns2 ns3; do for record in ns mx; do di
o.k. then why doesn't the slaved NS and MX records have this trailing
dot in the powerdns database?
On Tue, May 22, 2012 at 10:46 AM, Marc Haber wrote:
> On Tue, May 22, 2012 at 10:17:24AM +0200, Emiel van Berlo wrote:
>> The PowerDNS manual has a BIG warning that it's forbidden to have a
>> tra
On Tue, May 22, 2012 at 07:58:21AM +0200, Emiel van Berlo wrote:
> In PowerDNS the SOA from the slave zone has this value :
>
> ns2.danego.net. noc.danego.net. 2010110341 28800 1800 86400 86400
Is that dig output? Or from a bind zonefile? Or filtered database
content?
> And when we setup a Maste
Hi,
We have setup a PowerDNS 3.1 server and have added a slave zone.
The master is on a windows 2008 dns.
There is some confusion with the SOA.
In PowerDNS the SOA from the slave zone has this value :
ns2.danego.net. noc.danego.net. 2010110341 28800 1800 86400 86400
We read this warning from t
16 matches
Mail list logo
