DNS Configuration
Managing custom DNS records in DuploCloud
Last updated
Was this helpful?
Managing custom DNS records in DuploCloud
Last updated
Was this helpful?
DuploCloud automatically creates and manages DNS records for many resources you deploy, such as Kubernetes Services or VM hosts with public IPs, by integrating with your cloud provider’s DNS service. These DNS records are essential for routing traffic to your workloads and Services.
In most cases, DNS names are created automatically and can be customized within the DuploCloud Platform. However, you may sometimes need to manually configure or troubleshoot DNS entries, such as when using custom domain names, ensuring DuploCloud doesn’t overwrite DNS records you manage outside of the platform, or resolving DNS failures.
Configure your DNS zones: Make sure your DNS zones are properly configured in both DuploCloud and your cloud provider. This often involves setting up subdomain zones (like apps.mycompany.com) and connecting them to DuploCloud. See DNS setup instructions for your cloud provider:
AWS:
GCP:
Azure:
You can configure a custom DNS name for resource directly in the DuploCloud Platform, or manually in your cloud provider’s platform.
For resources that DuploCloud manages (like services behind Load Balancers), you can customize the automatically generated DNS name:
In the Tenant list box, select the Tenant.
Navigate to the Services page (Kubernetes -> Services, or Docker -> Services). The Services page displays.
Select your Service from the NAME column.
Click the Load Balancers tab.
In the DNS Name card, click Edit.
The prefix in the DNS Name is editable. Select a meaningful DNS Name prefix.
Click Save. A success message briefly displays at the top center of the DuploCloud Portal. Your new DNS name is now registered.
For resources that don’t have DNS configuration in DuploCloud (e.g., non-Kubernetes services), you will need to manually add DNS entries in your cloud provider’s DNS service.
If you create a DNS entry directly in your cloud provider’s platform (AWS, Google Cloud, or Azure), DuploCloud may delete it during updates, as it automatically deletes any DNS entries it did not create. To prevent this from happening, configure Systems Settings to ignore specific DNS entries.
From the DuploCloud Portal, navigate to Administrator -> System Settings -> System Config.
Click Add. The Add Config pane displays.
Fill the fields:
Config Type
AppConfig
Key
CNAME Prefixes to Ignore
Value
Enter the DNS prefixes to ignore. For example, entering test will prevent DuploCloud from deleting DNS entries like test.apps.duplocloud.net.
Click Submit. DuploCloud will ignore the specified DNS prefixes.
Occasionally, DNS resolution can fail on local machines, especially for private resources behind VPNs. This is often caused by incorrect DNS server settings or local DNS caching.
To fix this:
Use public DNS servers like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).
Flush your DNS cache.
Verify VPN connection if accessing private resources.
For AWS:
For GCP:
For Azure:
DuploCloud automatically deletes DNS records that it does not manage. If you create custom DNS names directly in your cloud provider, you must so they aren’t automatically removed.
