u/rschaaphuizen

For people managing DNS zones across multiple providers: how do you currently document why a DNS record exists?

Do you keep notes in your DNS provider, an internal wiki, Git, tickets, or not at all?

I'm building a DNS management tool and trying to understand how teams deal with stale records, SPF/DKIM/DMARC records, and provider-specific workflows.

I just have launched the first public page for Deenez at deenez.com

Deenez is a new tool i'm building to make DNS record management easier, especially when zones start getting messy across teams, providers, and environments.

The idea is to help with things like:

• grouping related DNS records
• adding notes/context to records
• normalizing record values
• integrating with multiple DNS providers
• composing more complex records like SPF
• optional SPF flattening
• linking records to resources, like servers, instead copy pasting ip addresses
• scheduling DNS changes or adding expiring dates
• keeping an audit trail of DNS record changes

If you'd like to keep posted. Make sure you sign up for the waitlist. If your would like a specific provider to integrate with, also let me know by filling in the form on the site.

Would also love to hear feedback from people who manage DNS regularly. What are the biggest pain points you’d like me to solve in this tool?

I just have launched the first public page for Deenez at deenez.com

Deenez is a new tool i'm building to make DNS record management easier, especially when zones start getting messy across teams, providers, and environments.

The idea is to help with things like:

• grouping related DNS records
• adding notes/context to records
• normalizing record values
• integrating with multiple DNS providers
• composing more complex records like SPF
• optional SPF flattening
• linking records to resources, like servers, instead copy pasting ip addresses
• scheduling DNS changes or adding expiring dates
• keeping an audit trail of DNS record changes

If you'd like to keep posted. Make sure you sign up for the waitlist. If your would like a specific provider to integrate with, also let me know by filling in the form on the site.

Would also love to hear feedback from people who manage DNS regularly. What are the biggest pain points you’d like me to solve in this tool?

Hi all,

I’m working on an idea for a DNS management tool and I’d love to get some honest feedback. Especially from people who deal with DNS in real-world environments.

The problem I keep running into is that DNS records often become messy over time:

• records are spread across different providers
• it’s not always clear why a record exists (especially when they don't have a recognizable name)
• values are entered inconsistently (for like CNAME records with a dot at the end or not?)
• SPF records become hard to maintain
• temporary records stay around forever
• changes are made without much context or history
• DNS changes are hard to plan, review, or audit

The tool I’m thinking about would focus on making DNS management more structured and understandable, especially for those who manage multiple domains.

Some of the features I have in mind:

• grouping related DNS records together
• adding notes/comments to individual records
• normalizing record values
• integrations with multiple DNS providers (like cloudflare, route53 etc)
• helping compose more complex records like SPF
• optional SPF flattening
• linking records to resources, such as servers, instead of manually entering IP addresses
• scheduling DNS changes
• audit trail for changes
• expiration dates for temporary records

I’m not trying to pitch anything here. I’m trying to validate whether this is a real enough pain point.

A few questions:

1. Is this something you would actually use?
2. What part of DNS management is most annoying or risky for you today?
3. Are there features missing from the list above?
4. If you manage DNS for clients or multiple teams, what would make this trustworthy enough for you to use?

Any feedback or criticism are very welcome. Also leave a reply like “please don’t build this” if you think nobody is waiting for a tool like this.