How does Make.com handle DNS resolution for integrated services?

Hello Make.com community,

I’m planning to update the IP address for an external service we’re integrating with Make.com. Our integration currently uses URLs that will remain the same, but we’ll be changing the IP address in the DNS records.

I have a few questions about how Make.com handles DNS resolution in this scenario:

  1. Does Make.com cache DNS resolutions for integrated services? If so, for how long?
  2. If there is caching, is there a way to manually clear the cache or force a DNS refresh for a specific integration?
  3. Are there any best practices or recommended steps when changing the IP address of an integrated service to ensure smooth operation with Make.com?
  4. Has anyone in the community experienced a similar situation? If so, what was your experience, and do you have any advice?

Any insights or information would be greatly appreciated. We want to ensure our integration continues to work smoothly after the IP change.

Thank you in advance for your help!

I wanted to follow up on my question about DNS resolution in Make.com and share the official response I received from support, as it might be helpful for others in a similar situation.

Official Response from Make.com Support:
According to their dev team, there are multiple components in the chain that cache DNS for short periods:

  1. Make.com’s infrastructure DNS respects the TTL of the resolved DNS entries
  2. Their services hold resolved DNS for the entire execution of a scenario

Important Note:
The support team recommended implementing redundancy during migration, meaning it’s best to have the service available on both IP addresses during the transition period.

This information should be helpful for anyone planning similar DNS changes for their integrated services. It’s good to know that Make.com respects DNS TTLs and that DNS resolution is maintained throughout scenario execution.

Hope this helps someone else in the future!

2 Likes