New maintainer for MSDNS needed!

[tlimoncelli]

We'll need a new maintainer of the MSDNS provider sometime between now and April 2025.

The current maintainer (me) will lose access the dev/test environment used for maintaining this environment around April 2025. At that time I'll no longer be able to work on the code, other than cosmetic changes that require no testing.

While that seems like a long time from now, I want to start seeking a new maintainer now. If nobody steps by by April 2025, this provider will go into the unsupported category.

Who would like to step up to maintain this provider?

[julian45]

I'm a DNSControl user and although I don't daily-drive with MSDNS (i.e., it's not one of the providers I regularly use with DNSControl) and I admittedly don't currently have much Go experience, I do have access to an MSDNS environment that could be used for test/dev. Perhaps I could take a stab at fixing an open issue or two; if successful, would that be acceptable towards becoming a maintainer for the provider?

[tlimoncelli]

Hi @julian45 !

Hey that'd be great! Looking at the list of MSDNS bugs I think #2599 and #2840 might be good starter projects.

https://docs.dnscontrol.org/developer-info/integration-tests is a good tutorial on running the test suite.

Please let me know how I can be of assistance!