Hi Eli,
To keep it simple, you could implement the solution outside the DNS server by
generating the different zones from a unified source, that contains both
information about each RR.
Winfried
Am 3. August 2022 01:43:38 MESZ schrieb eli glynn via Pdns-users
:
>I've recently inherited a
Both very fair suggestions :)
I should have stressed the fact that we already have a deployed set of
PowerDNS servers, spread across several datacenters and AWS regions, and
which a large number of (>2000) production systems are already hitting.
Ideally, we'd be able to update the existing PDNS
On 3 August 2022 6.53.11 UTC, Winfried Angele via Pdns-users
wrote:
>Hi Eli,
>
>On 03.08.22 01:43, eli glynn via Pdns-users wrote:
>> I've recently inherited a really ugly mess at my company, involving a muddle
>> of PowerDNS, Route53, NS1, and just about every mixed up interaction you
>>
Hi Eli,
On 03.08.22 01:43, eli glynn via Pdns-users wrote:
I've recently inherited a really ugly mess at my company, involving a
muddle of PowerDNS, Route53, NS1, and just about every mixed up
interaction you could imagine between them all.
The biggest part of the jumble is the way PowerDNS
I've recently inherited a really ugly mess at my company, involving a
muddle of PowerDNS, Route53, NS1, and just about every mixed up interaction
you could imagine between them all.
The biggest part of the jumble is the way PowerDNS was used as a poor-mans
split horizon - we have a large number
