DNS Zone in Azure Cloud

Question

I have been having a problem with a DNS Zone that I have provisioned in Azure Cloud. This has worked for over a year now, but it seems to have stopped working over the past month.

I use this DNS Zone as a part of the automation of SSL certificates using Posh-ACME inside of a bunch of Azure Devops pipelines.

The devops pipelines will create TXT records within the servcossl.work DNS Zone and then wait a few minutes for the TXT records to propagate so the SSL certificate can validate using the TXT record. However, the TXT records don’t seem to be propagating anymore. Please see the attached screenshot. I manually created the TXT record: acme-test.servcossl.work with a 30 second TTL so it still lives within servcossl.work. The highlighted TXT record: servcoforklift-acme.servcossl.work is an example of one of the TXT records that is automatically generated via the devops pipeline, and it has a 10 second TTL.

The problem is that these TXT records don’t seem to propagate anymore. I usually test using an online service like: https://dnschecker.org

I did notice that the DNS Zone lists a maximum number of record sets to be 10,000 so perhaps I’ve surpassed this limit during the lifetime of the DNS Zone!? However, I always create the TXT record and then delete it after the SSL certificate has been validated so there are really only 2 DNS records active at any time.