# duckdns\_not\_working

*/rant\_start*

This statement is **FALSE**..

I have seen that statement multiple times and **never** has that been the case.

DuckDNS is like a phonebook, it has **one** job and that is to assign a subdomain name to an IP,

If `my-ha-domain.duckdns.org` resolves to your IP then DuckDNS **is** working and you should check elsewwhere.

Verify this with `nslookup` on Windows or a webservice like <https://network-tools.com/nslook/>

nslookup:

```
C:\Users\user>nslookup my-ha-domain.duckdns.org
Server:  a0d7b954-pi-hole
Address:  192.168.2.200

Non-authoritative answer:
Name:    my-ha-domain.duckdns.org
Address:  127.0.0.1
```

*/rant\_end*


---

# Agent Instructions: 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:

```
GET https://ludeeus.gitbook.io/root/duckdns/duckdns_not_working.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.