> For the complete documentation index, see [llms.txt](https://docs.arkannis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkannis.net/cloud/aws/route-53/set-up-r53-dns-entry-for-gitbook.md).
# Set up R53 DNS Entry for GitBook
{% hint style="info" %}
**Note:**
You will require to have a domain already registered with AWS in order for this guide to work
{% endhint %}
## GitBook config:
1. Click **Publish**
2. Select either **Public** or **Unlisted**
3\. Click **Confirm**
4\. Click **Link and domain settings**
5\. Click **Connect a domain**
6\. Enter domain or subdomain name:
7\. Copy CNAME "link"
{% hint style="info" %}
This will be needed for the AWS DNS configuration
{% endhint %}
## AWS config:
Go to Route53 --> Hosted Zones --> Click Domain name --> Click Create Record
1. Set up Record Name
2. Select CNAME
3. Insert Github link you've recived earier
4. Click create record
5\. Click Retry in GitBook
{% hint style="info" %}
**Note:**
The DNS CNAME Record could take up to 30 minutes to update and propagate
{% endhint %}
### Resources:
[GitBook configure DNS](https://docs.gitbook.com/hosting/custom-domains/dns-configuration#configure-a-cname-record)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.arkannis.net/cloud/aws/route-53/set-up-r53-dns-entry-for-gitbook.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.