[GH-ISSUE #415] Add test that Kubernetes name lookup works correctly #481

New issue

Open

opened 2026-03-15 22:44:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-15 22:44:51 +03:00

Owner

Originally created by @briansmith on GitHub (Apr 20, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/415

Let's add a test that uses an /etc/resolv.conf like Kubernetes's default, which has a search path like .namespace-name.svc.cluster.local., .svc.cluster.local., .cluster.local. with ndots = 5. In particular, we should test that an application can use all/any of {service-name, service-name.namespace-name, service-name.namespace-name.svc, service-name.namespace-name.svc.cluster.local, and service-name.namespace-name.svc.cluster.local to reference a service service-name in the namespace namespace-name in the local cluster. With this test we can better support users of Trust-DNS within Kubernetes.

Originally created by @briansmith on GitHub (Apr 20, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/415 Let's add a test that uses an `/etc/resolv.conf` like Kubernetes's default, which has a search path like `.namespace-name.svc.cluster.local., .svc.cluster.local., .cluster.local.` with `ndots = 5`. In particular, we should test that an application can use all/any of {`service-name`, `service-name.namespace-name`, `service-name.namespace-name.svc`, `service-name.namespace-name.svc.cluster.local`, and `service-name.namespace-name.svc.cluster.local` to reference a service `service-name` in the namespace `namespace-name` in the local cluster. With this test we can better support users of Trust-DNS within Kubernetes.