Multiple Server IP Addresses

[mkeeton]

I currently use Vault for source control within a company network. Therefore the server IP address stored within my Visual Studio solution file is an internal IP (192.168......). Recently I needed to work from home, however found that when opening my solution it wants to connect to an internal IP and refuses to accept that I need to use a different address to connect to the server (which from home needs an external IP).
Unfortunately changing the IP in the solution then reverses the problem with the external IP not workign from within the company network.

Is there a way to get Vault to allow me to connect to the same server from the same solution but using whichever IP I tell it to depending on where I'm working from?

[lbauer]

Is it possible for you to use a fully qualified domain name instead of the IP address for your Vault Server connection?

[mkeeton]

I could use a server domain name internally, however the external IP does not have a domain name attached to it.

The problem is that whichever way I do it, the 1 server has 2 addresses depending on where I connect to it from.

[lbauer]

One option would be to use the external IP for both connections, and have your internal DNS routing set up to route the external IP to the right internal server.

[mkeeton]

I did raise that possibility with our internal IT support but was told that I'd be waiting forever for them to get round to it.
It's just a shame that the system can't just use the IP from the profile information saved in my client rather than one hardcoded into the solution file as that would solve the problem and surely the client could confirm that it was connecting to the right database using a database ID.

[lbauer]

Another option and maybe easier to set up -- allow internal users to use the external IP. It will just go outside the network and come back in. It might be slower than routing internally, but would get you something that works.