sekskant Blog

OVHcloud + Kubernetes: "DNSConfigForming" "Nameserver limits were exceeded" warnings on fresh 3-AZ clusters

Symptoms#

On 12 March 2026, I noticed that a “factory-fresh” OVHcloud 3-AZ Kubernetes cluster kept producing the following warnings:

kube-system   2m42s       Warning   DNSConfigForming   pod/cilium-fzc5z                           Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   2m6s        Warning   DNSConfigForming   pod/cilium-envoy-g5p2h                     Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   66s         Warning   DNSConfigForming   pod/cilium-operator-7d9cf667d8-dctk7       Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   61s         Warning   DNSConfigForming   pod/coredns-58886b47ff-b4g76               Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   57s         Warning   DNSConfigForming   pod/cilium-6w5k4                           Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   43s         Warning   DNSConfigForming   pod/ovhcloud-apiserver-proxy-9pwkh         Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   11s         Warning   DNSConfigForming   pod/coredns-58886b47ff-rwplp               Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   5s          Warning   DNSConfigForming   pod/ovhcloud-apiserver-proxy-4lbhm         Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8
kube-system   3s          Warning   DNSConfigForming   pod/cilium-envoy-tbqzg                     Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 213.186.33.99 1.1.1.1 8.8.8.8

On 23 March 2026, OVHcloud support told me the following:

This is a known issue on our side. We already prepared a fix which will be uploaded next month.

Apparently there is no good way to discover known problems like this in advance, which is also one of the reasons for this blog.

Timeline#

  • 12.03.2026

    First ticket created: on a freshly created 3-AZ Kubernetes cluster, continuous DNSConfigForming warnings appeared.

  • 19.03.2026

    Second ticket created, because the first one had been classified by the ticket system as "Information" and "Low Priority".

  • 23.03.2026

    OVHcloud support confirmed that this is a known issue on their side. A fix is planned to be rolled out starting in April.

About the Author Marco Borm

Marco Borm

Founder of the software company sekskant based in Hoppegarten near Berlin. 26 years of professional experience as a team lead, developer, and bridge between customers, product management and software engineering.

More Articles

  • OVHcloud + Managed PostgreSQL: Correct certificate validation with node "pg" module and payload
    DE | EN
    Apr 14, 2026
    OVHcloud + Managed PostgreSQL: Correct certificate validation with node "pg" module and payload

    Many managed database services, like the one from OVHcloud, offer TLS-secured connections to your database. But do you understand whether that actually makes you "secure" in your context, or whether you are still a good target for man-in-the-middle attacks? This article shares some insights from my own experience.

  • OVHcloud + VPS: Still no Ubuntu 25.10, only Ubuntu 25.04
    DE | EN
    Mar 27, 2026
    OVHcloud + VPS: Still no Ubuntu 25.10, only Ubuntu 25.04

    When setting up a VPS, it is worth checking which images the provider actually offers. At OVHcloud, the newest available Ubuntu version is still 25.04, even though it has already been out of support for a while. I asked them about it.

  • Payload + Turbopack + Windows: How to fix "Can't find stylesheet to import."
    DE | EN
    Apr 15, 2026
    Payload + Turbopack + Windows: How to fix "Can't find stylesheet to import."

    If you also have trouble running turbopack on windows and get "Can't find stylesheet to import." errors, this might help you.