Sharing & printing

Connect a custom domain when hosting supports it

Add a menu hostname, verify CNAME and TXT records, and understand why HTTPS must be ready before sharing.

5 min readUpdated

For: Restaurant owners and their domain administrator

In this guide

Check availability before changing DNS

From Web menu & QR, select Connect a custom domain. This feature is managed by the restaurant owner. If the page displays Available after hosting, a custom-domain connection is not ready in that environment. Continue using the restaurant’s working hosted Dishcard link; do not guess a CNAME destination.

A custom domain is an address such as menu.yourrestaurant.com. Adding it in Dishcard does not buy a domain or automatically complete HTTPS. Have the person responsible for your domain make the DNS changes, using the values shown for this connection.

Custom-domain configuration form Enlarge screenshot
A custom domain can be added when hosting is available. This local training example uses menu.example.test and does not show a verification secret.

Add and verify the hostname

  1. Enter the hostname in Domain, without a protocol, page path, or query string.
  2. Choose the destination Menu and select Add domain. Confirm that the new card shows the intended hostname.
  3. At your DNS provider, create the CNAME record pointing to the target displayed by Dishcard.
  4. Add the ownership record exactly as shown in TXT record name and TXT record value. Keep this TXT record while the connection is in use.
  5. Return to Dishcard and select Check DNS. Both the routing record and ownership record must match.
  6. If DNS is verified, complete the remaining HTTPS setup with the person managing your hosting. Open the final HTTPS address and check that it loads the correct guest menu without a certificate warning before sharing it.

DNS changes may take time to become visible. A DNS verified result confirms those records; the page explicitly notes that HTTPS setup is still required. It is not a promise that the new address is already ready for guests.

Resolve verification or connection problems

If the CNAME does not match, compare the exact hostname and target with the connection card. If ownership is not verified, check the TXT record’s name and value. DNS providers differ in whether they append your domain automatically, so check the resulting full record name.

If the domain is already connected to another restaurant, verify ownership and the intended restaurant before changing a connection. If the connection changed while you checked it, reload the page and review the current values. Adding a new domain requires editing access; if editing is paused, review billing first. The owner can still check or remove an existing connection.

Remove domain removes that Dishcard connection. Keep a tested standard menu link available before removing or changing a public address. Existing QR files keep their encoded target, so test and replace any material that points to an address you retire.

Reviewed against the current Dishcard app. Screenshots use sample restaurant data.

Screenshot