DNS setup oddity

[fortinj66]

Interesting response from nslookup on 4.10 nodes:

This is a vSphere IPI setup

[core@qa-c1v4-fd498-worker-kqzdr ~]$ nslookup yahoo.com
;; reply from unexpected source: 127.0.0.53#53, expected 10.102.5.64#53

;; Warning: ID mismatch: expected ID 36397, got 65524
Server:         10.99.111.1
Address:        10.99.111.1#53

Doesn't seem to be an issue, but this seems to be a new DNS characteristic...

/etc/resolv.conf

# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 10.102.5.64
nameserver 10.99.111.1
nameserver 10.99.111.2
search maeagle.corp qa-c1v4.os.maeagle.corp

[fortinj66]

This is fixed with #978