We now have two websites that we cannot reach from the inside our our domain/network. We don't have a DNS zone for these domains in our DNS and its not the same as our internal domain.
These domains have a forwarder on GoDaddy's public DNS to a page on our main website (https://domain.com/sitepage), this main website does not share a DNS zone in our internal DNS either. When we try this site outside of our DNS servers it works okay, some computers even work okay for one of the domains, totally weird. When you point DNS to Google on a computer that cannot resolve it, it works okay. When you ping the site from the outside and inside they go to the same IP which matches public DNS A records.
The only difference in when using NSLOOKUP is the server used to resolve the site, but it resolves to the same IP when we use our internal DNS.
Flushing DNS, registering DNS, clearing Cache on DNS servers, changing DNS server (3 DNS Servers) forwarders to something else does not seem to do the trick. All servers running Server 2012 R2 and Server 2016.
The webpage will end up telling you this (does not matter if you add https://
. or www.):
This site can’t be reached (website here) took too long to respond.
Search Google for (domain here) org