Vagrant box ubuntu/bionic64 DNS (Level3) suspicious behavior

[NYB]

I'm using the ubuntu/bionic64 vagrant box.

It seems that default DNS config is 4.2.2.1/4.2.2.2/208.67.220.220
However, it seems that Level3's DNS server are behaving suspiciously when requested for a domain that does not exist (and redirect to their own search engine that --i quote-- provides you with Yahoo! search results, which may include relevant sponsored links):

# dig i-dont.exist
; <<>> DiG 9.10.3-P4-Debian <<>> i-dont.exist
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36205
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;i-dont.exist. IN A

;; ANSWER SECTION:
i-dont.exist. 10 IN A 104.239.213.7
i-dont.exist. 10 IN A 198.105.254.11

;; Query time: 30 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Thu Jan 24 14:43:54 CET 2019
;; MSG SIZE rcvd: 62

# cat /etc/resolvconf/resolv.conf.d/original
nameserver 4.2.2.1 <-- these two are bad
nameserver 4.2.2.2 <-- these two are bad
nameserver 208.67.220.220

[Robert C Jennings (rcj)]

The nameserver is provided at runtime by the local DHCP server, these are not coded in the image. These are being injected by the infrastructure where your vagrant box is running. The code which creates this image is available for inspection @ https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-build/ubuntu-cpc/hooks/042-vagrant.binary?h=ubuntu/bionic-devel

Sorry to hear that your provider is doing this, it is frustrating. I'm going to close this as invalid as the image itself is not the source of this unfortunate behavior.