![rcode nxdomain rcode nxdomain](https://avinetworks.com/docs/17.2/avi-dns-policy/img/dns-actions-drop-down.png)
It is very important you use this with nslookup after anything you resolve or nslookup will try resolving every single DNS suffix you have set which can make it appear as if DNS is extremely slow. Replacing 1.1.1.1 with your VPN DNS server. In regards to the slow lookups, please try comparing a direct lookup against your DNS server.
#RCODE NXDOMAIN UPGRADE#
Our first suggestion is upgrade to 20H2 if you can, this fixes a slew of weird networking issues including some that might be effecting DNS compared to running 2004. Running a standard nslookup seems to timeout twice, then finally respond via the Viscosity DNS Server. The other DNS issue appears to be extremely slow DNS lookups.
![rcode nxdomain rcode nxdomain](https://munin.nwps.fi/nwps.fi/pihole.nwps.fi/unbound_munin_by_rcode-year.png)
The server profile is set to DNS Mode: "Automatic".
![rcode nxdomain rcode nxdomain](https://www.thebestcsharpprogrammerintheworld.com/wp-content/uploads/2020/07/image_thumb-1018.png)
Previously, this worked without issue prior to v1.9. I can manually fix this by adding a DNS suffix for within the network adapter itself. Most appear to function normally, but am unable to resolve second-level subdomains - e.g. The OpenVPN-based server I connect to pushes a number of DNS search domains. After upgrading and experiencing connection issues, I moved to the Viscosity Virtual Adapter and was successfully able to connect, but face some lingering DNS issues. Until v1.9 I was using the OpenVPN TAP Legacy adapter. However, I recently upgraded to v1.9 (1695) and encountered a slew of issues primarily relating to DNS. I've been a long-time user of Viscosity and have thankfully experienced a minimal number of issues.