DNS Resolver failing to deploy

Mike Matthews 1

We have a DNS Resolver as part of our Bicep configuration. This resource was first deployed some time ago, and the Bicep definition has not recently chagned. Our DevOps pipeline therefore does not need to modify it.

Starting this morning, however, the pipeline has been hanging and eventually failing when attempting to deploy the DNS Resolver. The specific error type is:

Microsoft.Azure.Networking.Dns.ManagedResolver.Frontend.Contracts.Exceptions.Service.FrontendServiceException

Our Bicep code is as follows:

resource dnsResolver 'Microsoft.Network/dnsResolvers@2022-07-01' = {
  name: dnsResolverName
  location: location
  properties: {
    virtualNetwork: {
      id: dnsResolverSubnetResourceId
    }
  }

  resource dnsResolvers_PrivateDNSResolver_name_InboundEndpoint 'inboundEndpoints' = {
    name: 'InboundEndpoint'
    location: location
    properties: {
      ipConfigurations: [
        { 
          subnet: {
            id: dnsResolverSubnetResourceId
          }
          privateIpAllocationMethod: 'Dynamic'
        }
      ]
    }
  }
}

ChaitanyaNaykodi-MSFT 26,936 Reputation points Microsoft Employee

2023-03-08T17:17:52.04+00:00

@Mike Matthews

Thank you for reaching out. I have reached out to the team internally regarding this issue and will make an update here as soon as I get a response. Thank you!
Jason Haley 5 Reputation points MVP

2023-03-18T14:20:40.8833333+00:00

I had a similar problem that went away once I changed the id to use a different syntax instead of the just the subnet variable reference.

so something like:
id: '${resolverVnet.id}/subnets/${inboundSubnet}'

instead of
id: dnsResolverSubnetResourceId

This github is where I found that resourceId syntax to use: https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.network/azure-dns-private-resolver/main.bicep
ChaitanyaNaykodi-MSFT 26,936 Reputation points Microsoft Employee

2023-03-21T20:32:06.8066667+00:00

@Mike Matthews

Apologies for the delayed response here. I was following up on a bug reported internally regarding similar issue. I see that the issue has been mitigated. Can you please confirm if you are able to run your dev ops pipeline now? Please let me know if you are still facing this issue. Thank you!
Mike Matthews 1 Reputation point

2023-03-22T09:12:18.4133333+00:00

Thanks @ChaitanyaNaykodi-MSFT

I can confirm everything is working as normal now.

Cheers,

Mike
Mike Matthews 1 Reputation point

2023-03-22T09:15:42.06+00:00

(And thanks Jason. I'll revisit your suggestion if this issue recurs.)
Tibo Jacobs 0 Reputation points

2023-06-02T06:36:36.87+00:00

Hi @ChaitanyaNaykodi-MSFT ,

I have tried the same solution as Jason but with me it still won't work. Are there any other solutions to this case?
Tibo Jacobs 0 Reputation points

2023-06-02T06:38:56.02+00:00

Hi,

I have tried the same solution as Jason but the issue still persist, are there any other known alternatives by now?

2 answers

Maarten Balliere 10 Reputation points

2024-06-05T20:52:53.1366667+00:00

Still not resolved, same issue here. Resource deploys but deployment fails. Any update?
Please sign in to rate this answer.

1 person found this answer helpful.
David-Sebastian Bahr 0 Reputation points

2024-08-27T11:59:23.7666667+00:00

I can confirm having the same issue, with the same error. I tried both syntaxes for referring to the subnet id, getting the same error.

I'm unable to provision an inbound endpoint for the resolver using Bicep.

@ChaitanyaNaykodi-MSFT is there any update on this?

Marcus Chaney 0 Reputation points

2024-12-17T14:08:37.9933333+00:00

I'm also having this issue also:

resource dnsResolver 'Microsoft.Network/dnsResolvers@2022-07-01' = { name: dnsResolvername location: location tags: { Environment: 'Hub' } properties: { virtualNetwork: { id: virtualNetwork.id } } } resource inboundEndpoint 'Microsoft.Network/dnsResolvers/inboundEndpoints@2022-07-01' = { name: '${dnsResolver.name}/Inbound' location: location dependsOn: [ dnsResolver ] tags: { Environment: 'Hub' } properties: { ipConfigurations: [ { subnet: { id: resourceId('Microsoft.Network/virtualNetworks/subnets', virtualNetwork.name, 'dnsSubnet') } privateIpAddress: '10.${hubCidr}.0.4' privateIpAllocationMethod: 'Dynamic' } ] } } resource outboundEndpoint 'Microsoft.Network/dnsResolvers/outboundEndpoints@2022-07-01' = { name: '${dnsResolver.name}/Outbound' location: location dependsOn: [ dnsResolver ] tags: { Environment: 'Hub' } properties: { subnet: { id: resourceId('Microsoft.Network/virtualNetworks/subnets', virtualNetwork.name, 'dmzSubnet') } } }

{"code": "BadRequest", "message": "Exception of type 'Microsoft.Azure.Networking.Dns.ManagedResolver.Frontend.Contracts.Exceptions.Service.FrontendBadRequestLegacyServiceException' was thrown."}

Tchimwa Sougang 946 Reputation points Microsoft Employee

2024-12-17T21:33:46.6633333+00:00

@Marcus Chaney

properties: { ipConfigurations: [ { subnet: { id: resourceId('Microsoft.Network/virtualNetworks/subnets', virtualNetwork.name, 'dnsSubnet') } privateIpAddress: '10.${hubCidr}.0.4' privateIpAllocationMethod: 'Dynamic' } ] }

You picked a static IP but choosing a Dynamic Allocation? Try to change "Dynamic" for "Static"
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Tchimwa Sougang 946 Reputation points Microsoft Employee

2024-12-17T21:31:46.4233333+00:00

properties: { ipConfigurations: [ { subnet: { id: resourceId('Microsoft.Network/virtualNetworks/subnets', virtualNetwork.name, 'dnsSubnet') } privateIpAddress: '10.${hubCidr}.0.4' privateIpAllocationMethod: 'Dynamic' } ] }

You picked a static IP but choosing a Dynamic Allocation? Try to change "Dynamic" for "Static"
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

DNS Resolver failing to deploy

2 answers

Your answer