Connect a domain with DNS and automatic TLS

Add the origin

Open Websites and choose Add website. Enter the domain without https:// or a path, then the IPv4 address of the server hosting your website. Choose its actual protocol and port. HTTPS commonly uses port 443 and HTTP uses port 80, but your origin may use a different port.

The origin address and proxy address serve different purposes. The origin field points to your website server. Your public A record must point to the Cloudhider proxy address displayed in the connection guide.

Update DNS

At your DNS provider, create or update an A record using the proxy IPv4 shown in Websites. For an apex domain, the record name is usually @ or an empty field. For a subdomain such as www, use that subdomain label. Keep your current nameservers.

Remove conflicting A records. An existing AAAA record must also route to this proxy over IPv6; otherwise remove that record while connecting through IPv4. Keep MX and other unrelated records needed by your email or other services.

Check DNS and TLS

Choose DNS setup, then Check DNS now. The panel sends a fresh DNS query and shows the check time. DNS caches still follow their TTL; repeatedly checking cannot force every resolver to update immediately.

Automatic TLS requires the domain's HTTP traffic on port 80 to reach Cloudhider's ACME challenge path. Manual TLS retry checks reachability immediately and starts or joins a serialized certificate job. Queued, checking DNS and issuing are separate states.

Verify the result

Wait until the certificate is active, open the website over HTTPS, then inspect its requests in Traffic & events. If the origin cannot be reached, verify its IP, protocol, port and firewall. Pausing a website deliberately returns HTTP 503; it does not change your DNS records.

Connecting through Cloudhider NS

Add a DNS zone, discover available records, import a zone file or create records manually. Check mail and third-party records for completeness. Verify ownership and publish records on both nameservers before changing delegation. If delegation already points to Cloudhider, the panel can verify ownership through NS.

Set ns1.cloudhider.ru and ns2.cloudhider.org at your registrar. When automatic activation is enabled, checks and subsequent steps run on the server. Regional routing requires ready nodes and a published record. Without changing NS, use the regular A-record connection.