How I can make contiv DNS Fwd to External DNS on Kubernetes

[newtonjose]

Description

Contiv create NAT rules to external DNS, but this don't work fine. So, its necessary create any thing configuration to work ok?

On tenant default this work good.

REF.: https://github.com/contiv/netplugin/blob/master/docs/dns.md

LOG from netplugin

time="Dec  5 18:13:22.870815406" level=info msg="Node proxy AddSvcSpec: kube-dns []" 
time="Dec  5 18:13:22.870857889" level=info msg="ProviderUpdate kubernetes [20.1.1.2]" 
time="Dec  5 18:13:22.870891505" level=info msg="ProviderUpdate kubernetes [20.1.1.2]]" 
time="Dec  5 18:13:22.870919026" level=info msg="Node proxy AddSvcSpec: kubernetes [20.1.1.2]]" 


time="Dec  5 18:17:34.986224634" level=info msg="lookup name-record: ;google.com.default.svc.cluster.local.	IN	 A " module=nameserver 
time="Dec  5 18:17:34.986346401" level=info msg="no name record: no record" 
time="Dec  5 18:17:34.986408836" level=info msg="lookup name-record: ;google.com.default.svc.cluster.local.	IN	 AAAA " module=nameserver 
time="Dec  5 18:17:34.986423235" level=info msg="no name record: no record" 
time="Dec  5 18:17:37.489212167" level=info msg="lookup name-record: ;google.com.default.svc.cluster.local.	IN	 A " module=nameserver 
time="Dec  5 18:17:37.489280807" level=info msg="no name record: no record" 
time="Dec  5 18:17:37.489344036" level=info msg="lookup name-record: ;google.com.default.svc.cluster.local.

Expected Behavior

from pod: ping google.com

Observed Behavior

Steps to Reproduce (for bugs)

• with cluster up

1. Create a tenant and network
2. Setting up a pod
3. And from inside the pod, ping on google

Your Environment

• netctl version
• Orchestrator version (e.g. kubernetes, mesos, swarm):
• Operating System and version