Comment 6 for bug 1794142

This may be a false alarm, when going through the yaml file in /etc/netplan on the MAAS VM and I noticed that the nameserver for the internal network was configured for an external network. I had Cisco remove those settings from the 172.x.x.x network entry. I should have confirmation tomorrow if this was in fact the issue. It now makes sense to me as to why the traffic was not resolved through the maas server once it was NAT'ed regardless of the hack. The yaml file now resembles the following:

network:
    version: 2
    ethernets:
        ens3:
            addresses:
              - 172.16.0.1/24
            dhcp4: no
        ens8:
            dhcp4: true