We have a public facing website eg. https://www.abc.qa (hosted by a vendor) and we have a forward Lookup zone in our internal DNS named eg. abc.qa. The forward lookup zone was created, so that our web application can be accessed using eg. https://hostname.abc.qa URL. The primary internal domain is eg. abc.local.
We are facing two issue due to this kind of setup - 1) Our external website is inaccessible internally within the domain (with or without www), however externally it works fine. 2) The web application is accessible internally. However, this web application is integrated with the website and so it communicates with the website through webservice and this communication does not works.
I researched about similar issues and found various solutions predominantly the one's below - 1) Adding netsh interface portproxy 2) Adding DNS delegation 3) Adding A or C record in DNS for the website.
None of the above works. I don't know why #1 doesn't works, but #2 and #3 are not applicable, as our website is hosted by a third party and they say the IP range changes frequently, so i cannot hardcode the IP.
Is there any other workaround apart from adding a subdomain or changing the internal forward lookup zone named abc.qa?