I am using k3s which relies on coredns to do dns look up. I am having a problem where I can not get kn to deploy one of my services on the local registry. It appears to imply lookup is failing, but I don't understand how. Below is a sample busybox run where dns is successful and the output I get from kn when I try creating said service.
[vagrant@master ~]$ kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup docker-registry
Server: 10.43.0.10
Address 1: 10.43.0.10 kube-dns.kube-system.svc.cluster.local
Name: docker-registry
Address 1: 10.43.172.19 docker-registry.default.svc.cluster.local
pod "busybox" deleted
[vagrant@master ~]$ kn service create knative-serving --image=docker-registry:5000/s3_receiverequest:0.0.1
Creating service 'knative-serving' in namespace 'default':
0.072s The Route is still working to reflect the latest desired specification.
0.138s ...
0.165s Configuration "knative-serving" is waiting for a Revision to become ready.
4.523s Revision "knative-serving-00001" failed with message: Unable to fetch image "docker-registry:5000/s3_receiverequest:0.0.1": failed to resolve image to digest: Get "
https://docker-registry:5000/v2/": dial tcp: lookup docker-registry on
10.43.0.10:53: server misbehaving.
4.546s Configuration "knative-serving" does not have any ready Revision.
Error: RevisionFailed: Revision "knative-serving-00001" failed with message: Unable to fetch image "docker-registry:5000/s3_receiverequest:0.0.1": failed to resolve image to digest: Get "
https://docker-registry:5000/v2/": dial tcp: lookup docker-registry on
10.43.0.10:53: server misbehaving