Mapping a Custom Domain to Your GitBook Documentation
Learn how to map a custom domain like docs.example.com to a GitBook space, including DNS setup, HTTPS activation, verification steps, and the limitations you need to know.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to map a custom domain like docs.example.com to a GitBook space, including DNS setup, HTTPS activation, verification steps, and the limitations you need to know.
Register a health-checked service, resolve it over Consul's DNS interface on port 8600, route .consul queries from the host resolver, and verify that failing instances drop out of answers.
Decide whether to use pfSense's Unbound resolver or dnsmasq forwarder based on DNSSEC needs, resource limits, and privacy preferences.
If DNS resolution fails on Fedora 38, the culprit is often a mis‑configured systemd‑resolved service. This guide walks through a diagnostic checklist, fixes tied to findings, and escalation steps to restore name resolution.
Learn how to add a custom domain to your ReadTheDocs project, configure DNS, update Sphinx, and verify the SSL certificate. Follow this step‑by‑step guide to ensure your docs load securely on your own domain.
Troubleshoot Scalingo HTTPS certificate failures: verify domain entry, DNS, propagation, rate limits, app restart, and platform logs, then apply fixes or escalate.
Learn how Consul Prepared Queries let you change service‑lookup filters (tags, version, health) without redeploying every client, with a worked example, trade‑offs, and practical steps.
Learn how to serve Read the Docs documentation on your own domain with HTTPS using only a CNAME record and RTFD’s automatic Let’s Encrypt integration.
Learn how to use Consul's health-aware DNS to prevent routing traffic to failing service instances, including configuration examples and DNS caching pitfalls.