> For the complete documentation index, see [llms.txt](https://docs.djangomango.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.djangomango.com/create-your-production-environment/point-your-domain.md).

# Point your Domain

At the moment, your droplet is only accessible via it's IP address. That may be fine for those that are looking to host a private application. But the majority of users are going to want a domain name they can attach to their server, and promote to others. And for that, you'll need to first register your domain.

{% hint style="info" %}
Note that you may also [reference the DigitalOcean guide](https://www.digitalocean.com/docs/networking/dns/how-to/add-domains/) for these steps.
{% endhint %}

### Register your Domain

If you already have a registered domain name, then great. You can jump straight to the next section. Otherwise, you'll need to register a domain name via your preferred registrar. If you aren't sure who to go through, we recommend [Google Domains](https://domains.google.com/registrar), they provide a great service, and you would be hard pressed to find a better nameserver provider.

### Configure your DNS records

You have the option of configuring your DNS records through your domain provider (if they provide the service), or using DigitalOcean's networking service. If you do decide to use DigitalOcean, then make sure you point your registrars nameservers to those provided by DigitalOcean before adding any DNS records and don't forget to add the nameservers via DigitalOcean's networking service.

Beyond that, adding DNS records is quite a simple affair. For the most simple setup, you'll only need to add an 'A' type record, which uses '@' as a hostname and redirects to your droplet IP address as the destination. For more complicated setups, including handing subdomains, forwards and other redirects, Google is your friend and should be able to provide context to any scenario you may have.


---

# 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.djangomango.com/create-your-production-environment/point-your-domain.md?ask=<question>&goal=<endgoal>
```

`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.
