Using VergeCloud NameServers

Seamlessly integrate VergeCloud’s CDN service by switching your domain’s NameServer (NS) to VergeCloud’s NS. This ensures all DNS queries are efficiently managed by VergeCloud, enabling enhanced control and optimization.

Introduction to DNS Settings

In the DNS Settings section of your VergeCloud dashboard, you can:

• Configure subdomains and resolve them to specific IP addresses.
• Toggle the Cloud Icon to determine which subdomains route through VergeCloud’s CDN and which connect directly to designated servers.

Supported Content

VergeCloud’s CDN is optimized to accelerate standard web content and public web services over ports 80 and 443. However, other services such as email, FTP, and similar non-web services must be handled differently.

Handling Email Issues

A common issue after transitioning to VergeCloud CDN is disruption in services like email. This occurs because email services rely on properly configured DNS records, which may need adjustments after switching to VergeCloud.

Steps to Resolve Email Issues

1. Verify MX Record Configuration: Ensure that the MX records are correctly set up in the DNS settings.
2. Create an A Record for the Email Server:
   
   • Create an A record pointing to mail.example.com (replace with your mail server domain).
   • Ensure the Cloud Icon is set to inactive (grey) to bypass the CDN.
3. Set MX Record to Point to A Record: Configure the MX record to reference the A record for the mail server.
4. Prioritize Multiple Email Servers: If multiple servers handle email traffic, set priorities to determine which server takes precedence.

Example DNS Setup:

A Record: 
  Name: mail
  IP Address: 192.0.2.10
  Cloud Icon: Inactive (grey)

MX Record:
  Name: @
  Target: mail.example.com
  Priority: 10

For email services such as Gmail or Zoho Mail, you only need to configure the MX records as specified by your provider. There’s no need to set up an A record.

Handling FTP and Other Services

To use FTP or similar services with VergeCloud CDN:

• Create a new subdomain (e.g., ftp.example.com) and set the Cloud Icon to inactive (grey).
• If the service requires a specific name to function, use the direct IP address of the server instead of a domain name.

Considerations

• Cloud Icon Settings: Enable the Cloud Icon for subdomains that should route traffic through VergeCloud’s CDN. Disable it (set to grey) for non-web services like email and FTP to bypass the CDN.
• Email Services: Ensure that MX records point to A records with the Cloud Icon disabled for email traffic to work properly.
• FTP and Other Services: Use a subdomain (e.g., ftp.example.com) or the direct IP address to connect services that require specific configurations.
• DNS TTL: Adjust the TTL settings for your DNS records to balance between quicker updates and caching performance.
• Testing Configurations: Use tools like dig or nslookup to verify DNS record configurations after making changes.