NS Lookup Failure when Nodus is a Primary CNI

The Nodus is the primary CNI. 

• When the POD subnet and the ovn-controller-network configmap are set to 10.244.0.0/16, the DNS lookup fails with the following error messages,

$ kubectl exec -it dnsutils – nslookup kubernetes.default

;; reply from unexpected source: 10.244.0.3#53, expected 10.96.0.10#53

;; reply from unexpected source: 10.244.0.3#53, expected 10.96.0.10#53

;; reply from unexpected source: 10.244.0.3#53, expected 10.96.0.10#53

;; connection timed out; no servers could be reached

• But when the POD subnet  and the ovn-controller-network are set to 10.158.142.0/18 (the default value configured in the ovn-controller-network, the dns seems to work fine

$ kubectl exec -it dnsutils – nslookup kubernetes.default

Server:         10.96.0.10

Address:        10.96.0.10#53

Name:   kubernetes.default.svc.cluster.local

Address: 10.96.0.1

•  But even in the second case above (where the DNS works fine) the emco-monitor errors out and getting restarted continuously on a multi-node cluster. Whereas it works fine in the single node cluster.

Is there any network configuration missing in the host?