Simone Carletti

> Datadog does [document](https://docs.datadoghq.com/getting_started/tagging/unified_service_tagging) `service`, `env` and `version` as tagging best practices. I am not sure how this applies to metrics. I can see service being populated for log entries,...

- Bind 9 supports it - PowerDNS authoritative doesn't support it, only recursor - NSD supports it - CF 1.1.1.1 resolver [supports it](https://developers.cloudflare.com/1.1.1.1/infrastructure/extended-dns-error-codes/)

> The change is now merged into `main` branch. [@weppos](https://github.com/weppos) do you want me to create `v9.0.0.RC1` release? Also, I see that on GitHub we're missing release `v8.1.0` even though...

@NelsonVides can you please take a look at this ticket. I was under the impression we removed the SPF completely. Perhaps we just needed to rollout v9 (which was done),...

Before we merge more changes, I'd like us to focus on the open core issues like the API. And ship a release with some changes, as we when bundle too...

It took me a while to follow up, as I had to spend some decent amount of time reading the RFC. I think the changes look great, they incorporate the...

After spotting that config, I decided to give it a shot to ask Claude to help me with comparing this PR with the RFC. This is what it found: ```...

> * Strict JSON Compliance: The JSON output format for zone responses has > been updated to be strictly compliant with the project's JSON file > format specifications. This ensures...

> That'd be easy to revert, but I was originally surprised by the format, the "content" key seemed a bit ad-hoc, it's not at all similar to the json payload...

> The previous format wasn't really well tested, and I wonder if it could have been a source of bugs, while the JSON format is already what all the API...