From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9976D9727B for ; Mon, 4 Mar 2024 15:11:59 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7205F18C44 for ; Mon, 4 Mar 2024 15:11:29 +0100 (CET) Received: from lana.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Mon, 4 Mar 2024 15:11:28 +0100 (CET) Received: by lana.proxmox.com (Postfix, from userid 10043) id 967142C235C; Mon, 4 Mar 2024 15:11:28 +0100 (CET) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Mon, 4 Mar 2024 15:11:28 +0100 Message-Id: <20240304141128.336180-1-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.350 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [powerdnsplugin.pm, powerdns.com] Subject: [pve-devel] [PATCH pve-network] fix #5275: remove priority field from powerdns X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2024 14:11:59 -0000 Since v3.4.2 the priority field has been removed and since v4.9 they are actively rejected by PowerDNS. Stop sending this field in order to make the PowerDNS plugin work with versions >= 4.9 again. [1] [1] https://doc.powerdns.com/authoritative/upgrading.html#api-changes Signed-off-by: Stefan Hanreich --- src/PVE/Network/SDN/Dns/PowerdnsPlugin.pm | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/PVE/Network/SDN/Dns/PowerdnsPlugin.pm b/src/PVE/Network/SDN/Dns/PowerdnsPlugin.pm index 096d131..5564120 100644 --- a/src/PVE/Network/SDN/Dns/PowerdnsPlugin.pm +++ b/src/PVE/Network/SDN/Dns/PowerdnsPlugin.pm @@ -69,8 +69,7 @@ sub add_a_record { my $record = { content => $ip, disabled => JSON::false, name => $fqdn, - type => $type, - priority => 0 }; + type => $type }; push @$final_records, $record; @@ -108,8 +107,7 @@ sub add_ptr_record { my $record = { content => $hostname, disabled => JSON::false, name => $reverseip, - type => $type, - priority => 0 }; + type => $type }; my $rrset = { name => $reverseip, type => $type, -- 2.39.2