colima fails to resolve some domains (max entries 16?)

### Describe the Issue
Some domains return a `Parse error` on nslookup on the colima ssh server, this in turn ends up creating an NX domain on the guest.

```
colima:~$ nslookup pubsub.googleapis.com
Server: 192.168.107.1
Address: 192.168.107.1:53

Non-authoritative answer:

Non-authoritative answer:
*** Can't find pubsub.googleapis.com: Parse error

colima:~$
```

This impacts guest machines as well, using dig on a guest machine works, but not the native resolver or nslookup.

#### Colima Version:

What is the output of `colima version`
```
colima version v0.4.2
git commit: f112f336d05926d62eb6134ee3d00f206560493b

runtime: docker
arch: x86_64
client: v20.10.16
server: v20.10.14
```
#### Lima Version:

What is the output of `limactl --version`
```
$limactl --version
limactl version 0.11.0
```
#### Qemu Version

What is the output of `qemu-img --version`
```
qemu-img version 7.0.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
```
### Operating System

- [X] macOS Intel
- [ ] macOS m1
- [ ] Linux

### To Reproduce

Steps to reproduce the behavior:

1. use the compose file below, run docker-compose up
2. docker exec into host
3. apt-get update && apt-get install dns-utils
4. nslookup `pubsub.googleapis.com` . Do a control check with `nslookup slashdot.org`

docker-compose.yml
```
version: "3.9"
services:
web:
image: "debian"
entrypoint: ["sleep","10000"]
```

### Expected behavior

The hostname should resolve.

### Additional context

It looks like it impacts hosts that have 16 response entries in them.