[FIXED] ARO DNS query issues when multiple custom DNS servers are configured

Solution Verified - Updated -


The issue described in this article has been fixed platform-wide. See the Resolution section.

Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.*

  • There is a dnsmasq issue that comes into effect when:

    • Custom DNS is configured in the ARO cluster following the ARO documentation.
    • Several nameservers are configured.
    • Name resolution targets a server other than the first one.
  • The issue will result in DNS timeouts and failed name resolution. However, it will not impact your cluster unless the DNS request targets one of the DNS servers that is not the first configured.


  • Red Hat OpenShift on Azure (ARO)
    • 4
  • OpenShift Managed (Azure)
    • 4
  • Custom DNS configuration
  • Multiple DNS servers

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content