Two considerations:
/etc/resolv.conf within the vfs is bad. Check /home/virtual/FILESYSTEMTEMPLATE/siteinfo/etc/resolv.conf. curl requests within an account use that information to check for DNS. It’s a special one-shot file, so it must first be unlinked, then recreated to copy data from /etc/resolv.conf on the server.
rm -f /home/virtual/FILESYSTEMTEMPLATE/siteinfo/etc/resolv.conf
upcp -sb apnscp/initialize-filesystem-template
Multihomed NIC, similar situation at this case.
That connection has a different DNS server configured: 8.8.8.8, 1.1.1.1, and 2600:1700:8461:b310::1.
For each IP, run the following command:
dig @IP +trace brickhouseofwashington.com
Depending how DNS is configured for the NIC, the offending resolver would be removed from /etc/sysconfig/network-scripts/ifcfg-DEV or /etc/NetworkManager/NetworkManager.conf. My money is on IPv6 resolver being invalid - either IPv6 missing from server or it’s an unrouteable address.