How is nslookup <service_name> resolved?

This page summarizes the projects mentioned and recommended in the original post on /r/kubernetes

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • CoreDNS

    CoreDNS is a DNS server that chains plugins

    Within a kubernetes container, the /etc/resolv.conf file is configured to point to a custom DNS server (or servers) that kubernetes manages. You can inspect this file pretty easily by execing into a pod and viewing the file. This file's contents will likely differ from the kube host's /etc/resolv.conf file, or any other computer you manage. Kubernete's managed dns server is configured to resolve dns queries against the service and/or pod directories. If a query can't be matched to a record, usually the managed dns server then queries another dns server. Usually this kubernetes-managed dns server is a [coreDNS](https://coredns.io/) server configured for a kubernetes cluster specifically, but one can [use their own configuration if they desire](https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/).

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts