Point your domain to a server or website

Find and edit destinations#

DynHost-managed names link to its section. DNS used by a web redirect is managed from its HTTP row. Redirects configured directly on an external web server are not listed in the portal.

TTL and target reflect DNS configuration; displaying them does not mean the destination website responds. Old values may stay cached for their TTL.

1. Open Redirects in the domain menu. On a phone, choose it under Manage my domain.
2. The list combines A (IPv4), AAAA (IPv6), CNAME records and portal-created 301/302 redirects. Existing DNS zone pointing records appear automatically.
3. Search for a name or destination and filter by type if needed.
4. Edit opens the form with current values. Delete requires confirmation and removes all values in that DNS row; other types remain.

To a remote server#

1. In Redirects, click To a server (IP or domain).
2. Leave the name empty for the root domain or enter a subdomain. Tick www if needed.
3. Choose IPv4 (A), IPv6 (AAAA) or domain name (CNAME). Enter only the IP or target name, without http:// or a path.
4. Review the summary. Tick replacement if you want to overwrite values of the same type, then publish.

Configure the target server#

The browser keeps your domain name. The remote hosting must accept this name and provide a matching HTTPS certificate. Pointing to an IP does not install a website, certificate or reverse proxy.

A CNAME cannot be used at the root or coexist with other types at the same name. Existing IPv6 remains when you change only IPv4: check both to avoid sending some visitors to the old server.

Pointing to 5.9.85.10 alone does not publish this portal under another name. Portal addresses are https://newtata.com and https://www.newtata.com; www redirects to the main name while keeping the requested page.

To another web address#

Choose To a web address (301/302), then a full HTTPS or HTTP URL. A 302 is temporary and useful for testing; a 301 indicates a permanent move.

MarocTech creates the required A record when the name is free. A target configured for another service causes rejection rather than implicit replacement. HTTPS is created on the first connection after DNS propagation.

Keep path forwards the path and query to the target. Deleting a redirect retains its A record, which you can reuse or delete later.