> For the complete documentation index, see [llms.txt](https://docs.ipaper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipaper.io/flipbook-integration/custom-domain.md). # Custom Domain ## Configuration Before iPaper can setup the Custom Domain module, you need to setup the domain on your end first. The subdomain can be anything you want, but let’s assume the following scenario: ``` Current catalog address: viewer.ipaper.io Main website: www.client.com Subdomain: catalogs.client.com ``` In this case, catalogs.client.com needs to be setup as a CNAME record pointing to the partner address. That is, the following CNAME record should be made: ``` catalogs.client.com => viewer.ipaper.io ``` If your catalogs are hosted through an iPaper partner, the CNAME alias should point to that specific partners address: ``` catalogs.client.com => {partner}.ipapercms.dk ``` {% hint style="warning" %} **Important:** The subdomain MUST be setup as a CNAME record, an A record will not work. If you have both External and Internal DNS, the CNAME record should be set up on both. {% endhint %} ## Verification To verify if the domain has been setup, you can use the following tool: Replace `publikationer.ipaper.dk` with the desired subdomain. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ipaper.io/flipbook-integration/custom-domain.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.