How to organize Service Discovery for iOS client?

Question

Domain Name System

Hello!
At present, I am still just learning, so there is not much experience in the development and design of systems, so I decided to turn to knowledgeable people.
The essence of the issue is as follows: an iOS application is planned, which acts as a thin client, and only requests information from the server and displays it. The question is, how best to pass to the client the address at which he should contact the server? Option - to sew it right away in the client is somehow not very good. I recently looked at Consul.io and got the idea to use DNS: create a domain (for example, service1.myapp.myname) and specify the desired service address as ip. So it will be possible without problems (I think so) to change ip as needed, and the application will always get the right ip for the same domain.
Are there any other options for solving this problem? I would like a solution that is more stable, since in my solution, by blocking the domain, clients will not receive the required address.

Answer 1

DNS is a surefire way to turn a name into an IP address, that's how the entire internet works.
For reliability, you can sew several addresses into the application by registering them with different registrars.
Some applications, like Skype, contain tightly packed server IPs inside, in case the client does not have DNS working.
The more tactics you apply, the more reliable the application will be.