Skip to content

Why can I not resolve private EC2 DNS names in my pods when nodelocal dns is used? #170

Answered by autero1
yorinasub17 asked this question in Help
Discussion options

You must be logged in to vote

If you’re having issues with non-cluster lookups with NodeLocal DNS deployed, check your (Corefile) configuration:

  1. Which DNS server the fallback .:53 queries are forwarded to:
 .:53 {
        ...
        bind 169.254.20.10 172.20.0.10
        forward . __PILLAR__UPSTREAM__SERVERS__ {
                prefer_udp
        }
        ...
}

Here, __PILLAR__UPSTREAM__SERVERS__ might resolve to 8.8.8.8 or some other custom DNS server, and subsequently fail to resolve the private EC2 DNS name.

  1. Optionally add extra configuration the private EC2 stubdomain, e.g.
us-west-2.compute.internal:53 {
        errors
        cache 30
        reload
        loop
        bind 169.254.20.10 172.20.0.10
    …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by autero1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
2 participants