DNS Custom Entries and History

Luke: yesssss! this is documentation at its core, change logs!

Michael S.: Hmm… honestly, I didn't think of using subdomains and this is a good idea, but, it doesn't make me jump for joy.
Primarily and before anything else, Hudu is not a monitoring tool, it's a documentation tool and the current domain features seem nice - but, not great.
To me, I simply want to document entire customer domains easier/better - this includes all the Office 365 ones (autodiscover/msoid/autoenrollment) and many many others for tools we use.
The fact is, you are right that I can add all these domains, but, it feels rather lackluster. We control the domains for ~75% of our clients, but, we do have the few that don't allow us and don't inform us of changes… e.g. I think we have all been involved in the situation where a web designer buggers up an entire client's O365 thinking they know what they are doing…
In the above situation, Hudu is kind of pointless if I then want to check the client's domain and I only see the new/incorrect details.
What I believe we should be able to do is to simply define a domain once - e.g. customer.com - then be able to simply type something like "autodiscover.customer.com / Cname" (amazing if we can import zone files/exports from other DNS tools) and then being able to "save" those results as the gold standard to a configuration entry for the client.
The value add for Hudu can then be to track all those entries and alert on when those entries change from the current values or similar.
Really, the same goes for some other areas - e.g. SSL Tracking/Whois tracking - It's all nice, but, in the event of an actual problem, it doesn't really make too much difference knowing what the details are now - we need to compare it to the past known/working solution.
I hope this makes a bit more sense and shows some of my thinking around this feature…
… Basically, If you have seen Liongard/Roar, it has no ability as a solo documentation platform, but, this is where it excels - being able to collect information easily and pump it in to IT Glue or other documentation tools as individual assets and keep everything up to date alongside comparing against past results.
To me, it's good - but too expensive for what you get and it feels rather like it exists solely because IT Glue (before Network Glue) exists as documentation and didn't really do any sort of population of documentation itself. Whilst I am not expecting Hudu to copy an entire product, a lot of these features seem to be the natural progression of any documentation tool.

William H. Considering that a subdomain is completely separate in terms of DNS, it should be entered separately as a different object. I feel that with the button to create and add another makes it easy to type in multiple at a time.
The ability to track dns changes and archive old entries like the other assets have already would be very nice. Perhaps there could be a way to group similar assets as well. For example, the ability to sort subdomains as a drop down or set of the primary, although this would be a cosmetic feature, not a functional one.
I can see perhaps the ability to add an “add related” entry that is within the domain, the thing that makes that tricky is that tricky is that since subdomains are separate assets, it would be harder to split alerts. For example, if I’m working on demo.example.com and take it offline because it’s a work in progress, I don’t want a status alert that example.com is offline. Hat would freak out a good bit of people. Demo would be a completely separate site/service.
This is why I think it is best that they are logically separate entries but it would be nice to be able to group them together for the sake of sorting and to make it easy to find them. Although there is the current ability to add relationships between assets. Maybe The Hudu Team can think of a way to expand upon this for domain monitoring.
One thing that I really like is that Hudu does the lookups from the local DNS instead of asking a public server that is hard-coded. This allows me to pull in local DNS entries that are different from public entries for development purposes and then enter a note under the asset about why it is different than the public IP.
The ability to annotate or add notes to asset revisions and explain why it changed would be a key feature here. That way we can document when that 3rd-party website mgmt firm borks the customer’s email or other asset when they don’t know what they are doing. :P