Forum Discussion

Peter Holland's avatar
Peter Holland
Iron Contributor
Apr 04, 2017

Azure Application Proxy Internal URL name resolution

Hi,

 

quick question about defining the 'internal URL' value for application proxy services...

 

my initial assumption was that the DNS resolution of the value you enter into the 'internal URL' field would be resolved by the connecter service installed on the internal servers.

 

In practice, from experience, it seems that the internal URL value is resolved by the application Proxy in Azure using external DNS..

or at least, if the internal URL you define is externally resolvable, it resolves the external DNS name, rather than the internal DNS name.

when the internal URL value isnt externally resolvable, that seems to work fine.

 

my validation is only based on defining an internal URL value which is resolvable by the connectors to the correct server/service and this resulting in a 'could not resolve....' error, whereas setting the internal server name or non-externally-resolvable value works.

 

in the old world of cauldrons, toil and trouble, hubble and bubble, and the likes of TMG, this might be performed using a hosts entry on the TMG box, which is obviously not possible with AAP.

 

is the above correct? should it be that way? or is there something else going wrong here? am i missing something (quite likely)?

 

Thanks 

 

Pete

App Services
azure
Networking

2 Replies

Sort By
  • Kent Gaardmand's avatar
    Kent Gaardmand
    Steel Contributor
    Apr 20, 2017

    im curious if you try to resolve the internal URL from one of the connector machines, does it resolve to an internal IP or external one ? are you running a split DNS scenario where the internal domain and external domain names are the same ?

     

     

    if you look at the deployment documentation here, the url must be resolved from the connector server.

    you actually confirm this "when the internal URL value isnt externally resolvable, that seems to work fine." and "whereas setting the internal server name or non-externally-resolvable value works."

     

     

    • Peter Holland's avatar
      Peter Holland
      Iron Contributor
      Apr 26, 2017

      Hi Kent,

       

      Many thanks for your response, my notification settings dont seem to be quite right in tech community currently so i hadnt seen that i had a reply.

       

      It appears that the issue i ran into was a transient problem on the connector server(s) as after a number of hours the publishing settled down and started working.

       

      The working settings were configured in such a way as to confirm that the internal URL defined is that which is resolved by the connector server.

Resources