Public Rest Service and DNS

[becyr]

Hi All, 

Help me out I am lost on DNS, Webadaptor and so on. 

We upgraded our gis server so now IT is helping us point the public url to the internal one. 

Our web adaptor is https://example/server/

I requested the below

1. Point https://example/server/rest/services to https://gis.example/arcgis/rest/services
2. Point https://example/portal/home/ to https://gis.example/portal/home/

If we point https://example/arcgis/rest/services to https://gis.example/arcgis/rest/services .would we need to update our web adaptor?

Correction* 

It's a new environment instead of an upgrade

[Scott_Tansley]

Ah.  Well you can’t have the same DNS pointed at two environments at the same time.  Typically my clients may have gis.example.com to begin with, but then a replacement environment may become maps.example.com.

otherwise you need to create a separate network (vlan) to host the new servers.  These servers will be isolated from the primary network.  You could then configure them as gis.example.com.

when configured you can retire the old server and cutover…. 

[becyr]

Thank you scott!! I did forward your comment to our IT department. 

I contacted Esri Tech support for further assistance. I got a heart-breaking response. It looks like our web adaptor which is https://begis2.us/server was used as a service URL when federating. Our gis.example public url would need to be added to the service url. This would in the end break the path of the data already published on Portal 😞

[Scott_Tansley · Accepted solution]

Yup.  That’s why you’d need the second dns.  I see this stuff all the time where enterprise deployments evolve rather than being planned.  There are some fundamental planning steps that are often overlooked.  Maybe I should write a book one day…. 

sorry you’re struggling. 

[becyr]

Yes, definitely. Thank you scott for troubleshooting with me.