Actions are unable to reach namesever specified in invoker dns config

I have a dns set up on 192.168.9.30.
My actions contains urls which needs to be resolved on this server but the actions are unable to reach the server and still reach out to kube-dns. Can someone please guide me. My invoker configs are

```
invoker:
imageName: "openwhisk/invoker"
imageTag: "1.0.0"
imagePullPolicy: "IfNotPresent"
restartPolicy: "Always"
port: 8080
options: ""
jvmHeapMB: "512"
jvmOptions: ""
loglevel: "INFO"
containerFactory:
useRunc: false
impl: "kubernetes"
enableConcurrency: false
networkConfig:
name: "bridge"
dns:
inheritInvokerConfig: false
overrides: # NOTE: if inheritInvokerConfig is true, all overrides are ignored
# Nameservers, search, and options are space-separated lists
# eg nameservers: "1.2.3.4 1.2.3.5 1.2.3.6" is a list of 3 nameservers
nameservers: "192.168.9.30"
search: "example.com"
options: ""
kubernetes:
isolateUserActions: true
replicaCount: 1
```

Start with the invoker.containerFactory.networkConfig.dns.overrides settings in the reported invoker configuration and trace how Kubernetes action containers receive DNS settings. Compare the configured 192.168.9.30 nameserver with the kube-dns behavior; done means action URLs resolve through the configured nameserver rather than kube-dns.

Written by the indexing model from the issue text.