Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
dns test failure when using kube-dns with dnsmasq 2.79
dnsmasq 2.79 introduced a change to respond to all norecurse queries with ServFail. This is to prevent cache snooping where an adversary can figure out if a particular hostname has been looked up or not.
http://www.thekelleys.org.uk/dnsmasq/CHANGELOG

We need to change the test to drop that flag, likely the intention was to not send the query upstream(outside of kubedns), but the flag will restrict the query to just dnsmasq.

One instance of the test failure:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke/31675#sig-network-dns-should-provide-dns-for-externalname-services

What you expected to happen:
The test should be fixed to drop the no recursion flag.
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/dns_common.go#L487

How to reproduce it (as minimally and precisely as possible):
Run kube-dns with dnsmasq 2.79.
dig +norecurse

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others: