Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve in-addr.arpa and ip6.arpa zones with CoreDNS kubernetes plugin #415

Merged
merged 1 commit into from
Mar 5, 2019

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Mar 5, 2019

  • Resolve in-addr.arpa and ip6.arpa DNS PTR requests for Kubernetes service IPs and pod IPs
  • Previously, CoreDNS was configured to resolve in-addr.arpa PTR records for service IPs (but not pod IPs)

Before:

$ dig 1.0.3.10.in-addr.arpa PTR
...
1.0.3.10.in-addr.arpa.  5       IN      PTR     kubernetes.default.svc.cluster.local.
$ 8.1.2.10.in-addr.arpa PTR
8.1.2.10.in-addr.arpa.  30      IN      PTR     ip-10-2-1-8.CLOUD_SPECIFIC_UPSTREAM

After:

$ dig 1.0.3.10.in-addr.arpa PTR
...
1.0.3.10.in-addr.arpa.  5       IN      PTR     kubernetes.default.svc.cluster.local.
$ 8.1.2.10.in-addr.arpa PTR
8.1.2.10.in-addr.arpa.  30      IN      PTR     10-2-1-8.prometheus.monitoring.svc.cluster.local.

Related:

* Resolve in-addr.arpa and ip6.arpa DNS PTR requests for Kubernetes
service IPs and pod IPs
* Previously, CoreDNS was configured to resolve in-addr.arpa PTR
records for service IPs (but not pod IPs)
@dghubble dghubble merged commit deec512 into master Mar 5, 2019
@dghubble dghubble deleted the reverse-dns-lookup-pods branch March 9, 2019 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant