Calling API by IP address vs domain name

Question

During a recent DDoS attack on a DNS, my site was unable to continue to function.

While the main site remained up and running, I was unable to connect to an external API on a different domain, leading the site to become completely unusable.

The data is fetched using PHP:

file_get_contents(API_PATH)

I currently call the API using the domain name, but I'm able to use the IP address if required.

Are there any advantages/disadvantages of calling the API by IP?

Is there anything else I should be aware of before making this change?

SOFe · Answer 1 · 2019-10-24T02:45:32.587

Your machine probably cached the resolved host, and has not updated it yet. You would need to flush the DNS cache.

It is not a good idea to use an IP address. While the DNS provider might be attacked, it is more likely that the IP is changed. I mean, rarely is a DNS provider attacked in such a large scale like the recent one, and it is definitely more common to see a website to have its IP address changed (although it shouldn't always happen normally). Therefore, you may want to use an IP address during a DNS attack (although your own DNS provider might be attacked as well), but not as the normal condition. If you want to be safe, fallback to use a cached IP address if the domain fails to resolve; but writing that kind of code is meaningless anyway, since it is rarely useful.

Edit: Removed the part about GitHub Pages, since it actually uses the `Host` HTTP header and has nothing to do with using DNS or not. — SOFe, Oct 24 '19 at 02:45

score 2 · Answer 2 · answered Oct 27 '16 at 13:36

2

If you use an IP address:

You can't move the service to a different server without updating all the client code
You can't use some forms of load balancing
You can't use the hostname to distinguish between multiple services hosted on the same IP address

answered Oct 27 '16 at 13:36

Quentin

914,110
126
1,211
1,335

score 1 · Answer 3 · answered Oct 27 '16 at 13:36

There really is not much difference in using the DNS name or IP address in your API calls.

However, If you ever change the service provider, you will have to update both your DNS settings (such as your A records) and the IP address in your code, you would not have to do this otherwise.

Other than that, pretty much good to go, unless someone else thinks of any other reason.

score 1 · Answer 4 · answered Oct 27 '16 at 13:39

I assume you want to mitigate the impact of the recent DNS DDoS attacks.

Advantages:

Your website still functions. Although that may not matter too much because nobody will be able to even visit your website.

Disadvantages:

What if the API changes its IP address?
What if the API does load balancing using DNS (e.g. it may resolve to different IPs at different times)?
What if the API uses a CDN?

I do not recommend it.

Calling API by IP address vs domain name

4 Answers4