Score:0

Master with Auto PTR creation - not syncing PTR records to slave?

au flag

I have a master server with a single zone sync'ing to a slave.

The slave has the same zone configured.

Both sides have the Auto PTR checkbox turned on. I've also tried with Auto PTR off on the slave.

I'm using mariadb as the backend

The master responds to reverse record lookups, the slave does not.

Is Auto PTR not supported in a master/slave setup (and I'm forced to create the zone manually?)

I have a "test.mydomain.local" record pointing to 1.1.1.1

The slave is reporting this:

 Nov 30 17:08:19 powerdns2 pdns_server[1881]: Received NOTIFY for 1.1.1.in-addr.arpa from 10.10.171.9 for which we are not authoritative, trying supermaster
Nov 30 17:08:19 powerdns2 pdns_server[1881]: Received NOTIFY for 1.1.1.in-addr.arpa from 10.10.171.9 for which we are not authoritative, trying supermaster
Nov 30 17:08:19 powerdns2 pdns_server[1881]: Error resolving SOA or NS for 1.1.1.in-addr.arpa at: 10.10.171.9: Remote nameserver replied with wrong id from 10.10.171.9

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.