We will be running a job soon where we want users to connect to a Internet based server but connect to a local server when on site due to slow network links. We will be subcontractors at the site and the infrastructure will be provided by the main client.
We'd like our application to try and connect to the local server first and if it fails or cannont find it then try the global server out on the Internet. I was thinking of using our domain registrar to create a project subdomain for each of the servers localproject.domain.com and project.domain.com as opposed to the devs having to use raw IP addresses in the app config.
I'm happy enough to give the project.domain.com the public Internet IP of the web server but can I give localproject.domain.com and internal 192.168.x.x address?
As for best practice should I instead be asking the client to add a DNS entry for localproject.domain.com to their LAN based DNS that we will be piggybacking off rather than having to make a trip to the Internet based DNS servers?