Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 fe80::d635:1dff:fe01:1232%2

Ross

11/6/23, 9:13 AM

I have a Kubernetes cluster - version 1.24.3 - consisting of four ubuntu 20.04 servers. The only problem is I get constant warnings regarding "Nameserver limits were exceeded..."

The image above is to highlight that this is happening on each node and to an excessive amount. Each message consists of:

Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 fe80::d635:1dff:fe01:1232%2

I have checked and people seem to point to the resolv.conf file containing to many entries. However, no answer explains if it is safe to remove certain entries. It also states in the file not to edit it.

How do I get it so that the warnings stop?

resolv.conf:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search broadband localdomain

2079

0 + 4

server

networking

dns

20.04

David

11/6/23, 9:16 AM

Please do not show pictures of text. Cut and paste into the body of the question. Pictures can not be searched, are often cut off and force the person trying to help to leave the question in order to see the pic.

Ross

11/6/23, 9:26 AM

The picture is there to highlight that it is happening to each node and at an excessive amount. The entire message is in the title. Unfortunately, there is no more to the message. I will highlight that in my question though.

muru

11/6/23, 12:56 PM

Are the errors from the k8s pods or the nodes? Is the `resolv.conf` you have shown from the pods or the nodes? Finally, other than this warning, is there an actual observable problem due to this?

Ross

11/8/23, 5:12 AM

I believe this is from the pods. The `resolv.conf` file shown above is from the nodes. but checking some of the pods `resolv.conf` file there are 4 entries. There is no observable problem caused by this, but I would prefer the warning not to be flooded but these warnings.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 fe80::d635:1dff:fe01:1232%2

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.