~ $ nslookup metrics-server
Server:         10.43.0.10
Address:        10.43.0.10:53

** server can't find metrics-server.cluster.local: NXDOMAIN

Name:   metrics-server.kube-system.svc.cluster.local
Address: 10.43.239.172

** server can't find metrics-server.svc.cluster.local: NXDOMAIN

** server can't find metrics-server.svc.cluster.local: NXDOMAIN


** server can't find metrics-server.cluster.local: NXDOMAIN

** server can't find metrics-server.lan: NXDOMAIN

** server can't find metrics-server.lan: NXDOMAIN

** server can't find metrics-server.local: NXDOMAIN

** server can't find metrics-server.local: NXDOMAIN

~ $ nslookup metrics-server.kube-system.svc
Server:         10.43.0.10
Address:        10.43.0.10:53

** server can't find metrics-server.kube-system.svc: NXDOMAIN

** server can't find metrics-server.kube-system.svc: NXDOMAIN

I got the above result in a fresh k3s cluster. I am pretty sure I was able to resolve service without the "cluster.local" suffix a few weeks ago. In the 2ns nslookup, it seems it won't perform the search function. Any idea what's wrong?