Where Should I Configure DNS Resolvers in Coolify for n8n?

Below is some guidance on troubleshooting DNS-related issues for the HTTP Request node. Note that the HTTP Request node itself doesn’t contain settings for DNS resolvers; it relies on the DNS configuration of the environment where n8n runs. Here are a few steps to consider:

1. Container-Level DNS Settings

If n8n is running in a Docker container (which is often the case with installations managed by Coolify), the container’s DNS resolvers are defined at the Docker level rather than in Coolify’s web UI. You can add a DNS section in your Docker Compose file (or adjust the container run settings) to force n8n to use specific DNS servers. For example:

YAMLCopied
services:
  n8n:
    image: n8nio/n8n
    dns:
      - 1.1.1.1
      - 8.8.8.8
    # ... other options

If you’re not directly managing a Docker Compose file (because Coolify does it for you), check if Coolify lets you pass additional Docker settings or environment variables that control DNS resolution.

2. Host-Level DNS Configuration

If the containers are relying on the host’s DNS configuration, ensure that your Contabo VPS is set up to use the correct resolvers. This typically means checking the contents of /etc/resolv.conf on your VPS. The nameserver entries here should include the DNS resolvers you want (e.g., 1.1.1.1 and 8.8.8.8).

3. Coolify Settings Versus Docker Settings

The DNS settings you added in the Coolify UI (found under Settings > DNS Validation) may only affect how Coolify validates domains and not the DNS lookup done by containers. The HTTP Request node uses the underlying system’s (or container’s) DNS settings. Look for a way to override DNS settings for container processes in Coolify’s configuration for your n8n app.

Summary

• Container/Docker Level: Ensure your container definition (via Docker Compose or run command) includes a proper DNS configuration.
• Host Level: Verify the VPS’s /etc/resolv.conf contains the desired DNS servers.
• Coolify Integration: Investigate if Coolify provides an option to pass these settings to the container runtime rather than using the DNS Validation UI alone.

In short, while Coolify’s DNS Validation setting helps for validating your domain names, resolving the HTTP Request node’s DNS issues usually involves adjusting the DNS settings at the Docker container (or host) level.