issues
disappeared.
- Dave
On Wed, Nov 24, 2021 at 12:58 PM Thomas via Pdns-users
wrote:
Added an 'API-RECTIFY = 0' to the zone meta-data having the
deadlocks and the deadlocks did not reapear until now.
Am 24.11.2021 um 10:38 schrieb Thomas via Pdns-users:
Hell
Added an 'API-RECTIFY = 0' to the zone meta-data having the deadlocks
and the deadlocks did not reapear until now.
Am 24.11.2021 um 10:38 schrieb Thomas via Pdns-users:
Hello.
We are running pdns-4.5.1-1pdns.el8.x86_64 with MariaDB-server-10.4.21
as backend. I am seeing regular m
Hello.
We are running pdns-4.5.1-1pdns.el8.x86_64 with MariaDB-server-10.4.21
as backend. I am seeing regular messages in our pdns 4.5.2 regarding
deadlocks in MySQL.
Exception: GSQLBackend unable to nullify ordername and update auth for
ovpn.spotsystem.net for domain_id 17651: Could not exe
Thanks for the answer.
Opened a ticket on github regarding the documentation.
Greeting,
Thomas
Am 05.10.2021 um 10:35 schrieb Pieter Lexis via Pdns-users:
Like a CNAME, only one ALIAS per name is allowed. It looks like the
documentation[1] does not make this clear
Sorry for the hurry, forgot some essential information.
We are running PDNS Authoritative 4.5.1 and pdns-recursor 4.5.5 to
resolve the alias records on RockyLinux 8.
Am 05.10.2021 um 09:00 schrieb Thomas via Pdns-users:
Hello.
We have switched lately to PowerDNS Authoritative Server and a
Hello.
We have switched lately to PowerDNS Authoritative Server and a Customer
signaled a modified behaviour of PDNS regarding ALIAS Records.
He has multiple alias records with the same name pointing to different
servers. The old DNS Server returned multiple A Records, as happends
with multipl
enough to do to not go in
timeout.
Thanks,
Thomas
Am 29.09.2021 um 11:08 schrieb Pieter Lexis via Pdns-users:
Hi Thomas,
On 9/29/21 10:46, Thomas via Pdns-users wrote:
Hello.
We are testing pdns and would like to migrate to it in few days. Now I
have seen errors showing up in the pdns logs wh
Hello.
We are testing pdns and would like to migrate to it in few days. Now I
have seen errors showing up in the pdns logs when I first query a domain
and (I presume) this domain is not in cache of pdns.
Error ist the following:
Backend reported permanent error which prevented lookup (GSQLBa
Am 22.06.2021 um 17:27 schrieb Brian Candler:
On 22/06/2021 16:16, Thomas via Pdns-users wrote:
Thanks for the clarification, but this scares me. How can I have
configured the server in a way it thinks it is authoritative for the
entire Internet?
It should be authoritative for zur-sonne.it and
for sihosting.cloud)
For that dig command line, when talking to an authoritative nameserver,
I'd also recommend you add the "+norec" flag, which makes it explicit
that you don't want to recurse.
Am 22.06.2021 um 16:54 schrieb Thomas via Pdns-users:
Am 22.06.2021 um 16:16 sch
Am 22.06.2021 um 16:16 schrieb Brian Candler:
On 22/06/2021 14:55, Thomas via Pdns-users wrote:
I have upgraded pdns authoritative server from version 4.3 to version
4.4.1 on CentOS 7, MySQL is the backend.
If I query a CNAME record on both servers I get the following error
(do not remember
Hello,
I have upgraded pdns authoritative server from version 4.3 to version
4.4.1 on CentOS 7, MySQL is the backend.
If I query a CNAME record on both servers I get the following error (do
not remember if it worked before the upgrade):
[root@pdns1 log]# nslookup www.example.it localhost
Serv
Good evening
We're a small company and we would like to replace a bind9 DNS Server and we're
not yet sure how we should setup PowerDNS.
The current configuration looks like this:
- Bind9, 1 master and 1 slave Server
- 8 very small DNS zones for partners, each Zone has just
13 matches
Mail list logo
