Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

What happened:
Windows pods are not getting the expected DNS suffix list. They are only getting the one for their current namespace and the Pod DnsPolicy is ignored

How to reproduce it (as minimally and precisely as possible):

Windows pods still only get the dns search suffix for their namespace. They should also have svc.cluster.local and cluster.local so that services can be resolved for other namespaces.

Here's /etc/resolv.conf on Linux

kubectl exec -i busybox-sleep cat /etc/resolv.conf
nameserver 10.0.0.10
search default.svc.cluster.local svc.cluster.local cluster.local g5hqkyfpy0nuzckf3igv405gkg.xx.internal.cloudapp.net
options ndots:5

Windows should have the same DNS search suffix results, but it only has the current namespace:

$ kubectl exec iis-1803-688b96c57b-s6657 ipconfig

Windows IP Configuration


Ethernet adapter vEthernet (f6667ee9-eth0):

   Connection-specific DNS Suffix  . : default.svc.cluster.local
   Link-local IPv6 Address . . . . . : fe80::8193:c234:bebb:93db%27
   IPv4 Address. . . . . . . . . . . : 10.240.0.136
   Subnet Mask . . . . . . . . . . . : 255.240.0.0
   Default Gateway . . . . . . . . . : 10.240.0.1

Anything else we need to know?:

• Also reported at DNS search suffix list is incomplete on Windows Azure/azure-container-networking#206
• Issue DNS servers and search domains are not set for Windows Pods #61579, PR Setup dns servers and search domains for Windows Pods #63905, (pending revert Setup DNS for Windows containers #66588) was an attempt to fix this, but it didn't work because the DNS server list needs to be passed to CNI, not Docker.

Also reported at Azure/azure-container-networking#206

Environment:

• Kubernetes version (use kubectl version): v1.11.1
• Cloud provider or hardware configuration: Azure (acs-engine v0.20)
• OS (e.g. from /etc/os-release): Windows Server version 1803

/sig windows
cc @daschott