Re: selective forwarding resolver that isn't being selective

I'm starting to notice peculiarities of the Kubernetes + Calico + Istio environment that the server is running in. Haven't determined if that's the cause yet. But Istio adds iptables nat rules *into the container* that affect port 53 communication. IDK how it affects it yet, but I raised it on t

Re: selective forwarding resolver that isn't being selective

Doug Freed wrote: > It would be helpful if we could see your actual BIND configuration Thanks for replying. Attached. include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; acl internals { localhost; /* internal CIDRs */; }; // internal systems options { version

Re: selective forwarding resolver that isn't being selective

On 8/20/25 12:27, Mike wrote: I set up BIND9 9.20 as a container in a Kubernetes cluster so that it could provide DNS services for all of my internal systems, via an "internal" view. Currently it also provides authoritative responses for some secondary servers in a hidden master configuration, bu