Tom Misilo

So I wonder if this is where RFC 4183 might be a good option? `-.2.0.192.in-addr.arpa` ([RFC 4183](https://www.rfc-editor.org/rfc/rfc4183.html) style) 10.130.90.0/23 -> 90-23.130.10.in-addr.arpa. So a snippet I believe should be ``` D('90-23.130.10.in-addr.arpa',...

I can take a stab at it! Though, I am wondering if it would make sense to add a feature flag that allows for specifying using RFC 4183 or RFC...

Just putting this here for notes Given a candidate network of the form `x.y.z.n/m` create an in-addr.arpa candidate domain name: 1. If the number of mask bits m is greater...

So I couldn't get it to create a new zone for a random domain, since I am thinking it is looking for a matching domain, This is actually the full...

If I do the following, I get the same result: ``` D('0/25.100.25.10.in-addr.arpa', NO_REGISTRAR, DnsProvider(AWS) ); ``` ``` Adding zone for 0/25.100.25.10.in-addr.arpa to route 53 account ERROR: ERROR: Domain 0/25.100.25.10.in-addr.arpa not...

I wonder if it is because this is what AWS is showing? `0/25.100.25.10.in-addr.arpa` I am wondering if AWS needs to be 0-25.100.25.10.in-addr.arpa instead, but not finding any helpful documentation or...

From: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DomainNameFormat.html?icmpid=docs_console_unmapped#domain-name-format-hosted-zones > If the domain name includes any characters other than a to z, 0 to 9, - (hyphen), or _ (underscore), Route 53 API actions return the characters...

@geerlingguy any suggestions on what to do? I am running into this trying to setup a new server on Ubuntu 22.04. We disable / mask apparmor, so it isn't apparmor...

I made a PR that will initialize a custom data directory. This does not handle any AppArmor issues, since we made the decision at this point to disable AppArmor locally.

not stle On Sat, Dec 9, 2023 at 2:58 PM github-actions[bot] ***@***.***> wrote: > This issue has been marked 'stale' due to lack of recent activity. If > there is...