Skip to main content

Setup Your Hosts

Configure your hosts to work with CycleDNS. This step involves setting up the devices or services that will report their IP addresses to CycleDNS for automatic DNS updates.

Understanding Hosts in CycleDNS​

A hostname in CycleDNS represents a device, server, or service that you want to track and update DNS records for. Each hostname can have:

  • A DNS record (type A)
  • Custom update intervals (via desktop/console client app)
  • Notification settings

Step 1: Access Host Management​

  1. Log in to your CycleDNS dashboard at dash.cycledns.com
  2. Navigate to "Hostnames" in the main menu
  3. Click "Add Hostname"

Step 2: Basic Host Configuration​

Host Information and Configuration​

Fill in the basic information:

  • Subdomain: The subdomain that will be updated (e.g., "home", "server", "api")
  • Domain: Select the provider zone this host will update
  • IPv4: You need to set an initial ip address, 127.0.0.1 is the recommended way
  • TTL: Time to live is the amount of time, in seconds, that a DNS record is cached by resolvers before it must be refreshed from the authoritative server
  • Enable URL for updates: If you disable your Desktop/Console clients as you update URL will stop functioning preventing new ip updates to the hostname

For security reasons, CycleDNS does not permit the creation of hostnames that already exist within your provider’s DNS zone. If you would like CycleDNS to manage an existing hostname, you must first delete it from your Cloudflare zone. Once removed, you can create and manage the hostname directly through the CycleDNS platform. Please note that CycleDNS only manages hostnames created within the platform.

Step 3: IP Detection Method​

Choose how CycleDNS will detect your host's IP address:

  • Public IP Detection: CycleDNS automatically detects your public IP
  • Best for: Most home and office setups
  • Requirements: Host must be able to make outbound HTTPS requests

Option B: Manual IP Entry​

  • Static IP: Enter a fixed IP address
  • Best for: Servers with static IPs
  • Use case: When you want to manually manage the IP

Step 4: Advanced Configuration​

Security Settings​

  • Update URL: Keep the hostname's Update URL private, don't share to anyone.

Step 5: Testing Your Configuration​

Troubleshooting​

"DNS Update Failed" Error

  • Verify Cloudflare API token permissions
  • Check that the zone is active
  • Ensure the subdomain doesn't conflict with existing records