Azure Private DNS Resolver deployment failing with circuit breaker

James Smith 0 Reputation points
2023-05-04T17:48:19.5166667+00:00

I am trying to deploy an Azure Private DNS resolver via the Azure Portal and I'm getting an obscure message about "Operation has exceeded maximum processing count." and "circuitBreaker=[state=Open, processedCount=6, maxProcessedCount=5]"

{
    "status": "Failed",
    "error": {
        "code": "InternalServerError",
        "message": "Operation has exceeded maximum processing count. dnsResolverResourceId=/subscriptions/xxx/resourceGroups/xxx/dnsResolvers/xxx, circuitBreaker=[state=Open, processedCount=6, maxProcessedCount=5]"
    }
}


The inbound subnet and outbound subnet are both dedicated /24's that are delegated to Microsoft.Network/dnsResolvers. I just have one virtual network and want the resolve to help with VPN client traffic.

I'm trying to deploy this in Canada Central

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,775 questions
{count} votes

6 answers

Sort by: Most helpful
  1. Joel Basham 0 Reputation points
    2024-09-18T04:15:46.1+00:00

    I was trying to deploy yesterday 17th September 2024 and received same erorr. I had this error via bicep deployment and via clickops in the portal. If your getting this issue in portal then there is nothing much you can do as a consumer .... I logged a support ticket, Azure support came back that it was a backend problem with the dns resolver service in Australia East region ....

    here is my error:

    {

      "code": "InternalServerError",

      "message": "Operation has exceeded maximum processing count. dnsResolverResourceId=/subscriptions/4d8b1cb3-9953-4173-b603-88890be2d8a7/resourceGroups/rg-sandpit-dns-resolver/dnsResolvers/dnsr-sandpit-core-01, circuitBreaker=[state=Open, processedCount=6, maxProcessedCount=5]"

    }

    Here is the email back from Azure Support.

    I have investigated this issue and it appears a close match to Platform issue with DNS resolver in multiple regions yesterday. This issue has been resolved around midnight yesterday in Australia time.

    May I request you to run operation again and update me in case there are still issues.

    Hope this helps someone.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.