> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/connectivity/domains-and-dns/how-tos/create-glue-records.md).
# Create glue records
***
If you want to run your own DNS servers with names matching the domain name, such as *ns1.example.se* and *ns2.example.se,* under the domain *example.se*, you need to create something called *glue records*. Glue records allow other DNS servers to look up the IP addresses of your nameservers. This is necessary because other nameservers on the internet need a way to find your domain's DNS servers before they can locate the domain's records within those servers. Glue records make this possible.
**Note that glue records only need to be created under these specific conditions, which is why the function is hidden by default. Furthermore, glue records can only be created for the top-level domains .SE and .NU.**
To create a glue record, click **Change nameservers** in the domain's overview.
When you enter a nameserver that shares the same domain part as the domain name, a new field for IP addresses will appear. Enter one or more IP addresses for the nameserver in this field. Once you’re done, click **Change nameservers**.
---
# 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.glesys.com/products/connectivity/domains-and-dns/how-tos/create-glue-records.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.