status_checks.py checking for default domain A record

[jasonnet]

I've just installed the latest miab about a week ago with a first domain and have been adding additional existing domains since. I'm using cloudflare dns for all the additional domains. This has gone well for all my mostly unused domains, but today I encountered something odd with a domain that includes a website.

For the domain manyedges.com I have a website that I want to continue to support. As a result, I've used the admin site to ask miab to customize the zone file to include a CNAME record for @ and www. that will point to the domain's main website.

But it seems that status_checks.py / check_dns_zone() is unhappy about this and grades the resulting zone file has having an error. The code seems to look for an A record for @ pointing to the box ip addr. If it is not the case, it treats this as an error.

Should we treat this as a miab bug/limitation, or should I just shrug this off, or... ?

[jasonnet]

Digging a bit deeper...

The box admin can fix this by not specifying a CNAME @ record for a domain. (A footnote on the cloudflare admin page suggests that creating such a record is deprecated but if the admin attempts it, CloudFlare will work around the deprecation with CNAME flattening.) Instead the box admin should provide an A record even if that means multiple fqdn have A records pointing to the same ip addr.

A suggested update to box would be to discourage the user from creating such a record in the custom dns page or to do CNAME flattening just like CloudFlare.