<p>When you add or alter a DNS record you need to update the serial number in the zone data and take into account the TTL (time to live) which is used by clients as a cache refresh interval. </p>

<p>If you are using a hosting provider's web-based control-panel, it probably takes care of the serial number for you but it won't adjust the TTL in advance of the change. Therefore your change can take a while to propagate through third-party and client DNS caches.</p>

<p>NXDOMAIN means "no such domain" - so far as the nearest DNS server is concerned, it has a still-valid set of data for the parent zone and that does not contain the delegation you enquired about.</p>

<pre><code>$ dig +nocmd +multiline +noall +answer machinenode.de
machinenode.de.         600 IN A 50.63.202.40

$ dig +nocmd +multiline +noall +answer dnsseed.machinenode.de
dnsseed.machinenode.de. 30 IN A 92.242.132.15
</code></pre>

<p>Those numbers 600 and 30 are the TTL values.</p>

CC BY-SA 4.0
2018-12-05T15:50:49.193Z
Okay thanks, however I've added those records few days ago (after registering the domain)...atleast the dnsseed. one
Nigho
CC BY-SA 4.0
2018-12-05T18:21:51.780Z
also, if I do `dig -t NS dnsseed.machinenode.de @ns01.machinenode.de` it works fine
Nigho
CC BY-SA 4.0
2018-12-05T15:28:10.310Z
2018-12-05T15:38:13.453Z
2018-12-05T15:38:13.453Z
RedGrittyBrick
<p>I wanna setup a dnsseed for a crypto currency using <a href="https://github.com/sipa/bitcoin-seeder" rel="nofollow noreferrer">sipa/bitcoin-seeder</a> on my VPS.
The server is hosted at NetCup and running the software as root, and also listening on port :53 UDP.</p>

<p>My domain is hosted at GoDaddy and got those records:</p>

<pre><code>dnsseed.machinenode.de  1800     IN     NS  ns01.machinenode.de.
ns01    1800     IN     A   SERVER_IP
</code></pre>

<p>However, if I use <code>dig -t NS dnsseed.machinenode.de</code> I just get <code>NXDOMAIN</code> as status and no namserver returned.</p>

<p>Is anyone familar with setting up a dnsseed and able to help?</p>

<p>Thanks and friendly regards</p>

<p>Nico</p>

<p><strong>EDIT:</strong></p>

<p>After switching my servers OS from CentOS 7 to Ubuntu 16.04 things started working.</p>

<cryptography><domain-registering>
Setup bitcoin-seeder
Nigho
# Setup bitcoin-seeder

(Asked by: username_0 on 2018-12-05)

I wanna setup a dnsseed for a crypto currency using sipa/bitcoin-seeder on my VPS.
The server is hosted at NetCup and running the software as root, and also listening on port :53 UDP.
My domain is hosted at GoDaddy and got those records:
dnsseed.machinenode.de  1800     IN     NS  ns01.machinenode.de.
ns01    1800     IN     A   SERVER_IP

However, if I use dig -t NS dnsseed.machinenode.de I just get NXDOMAIN as status and no namserver returned.
Is anyone familar with setting up a dnsseed and able to help?
Thanks and friendly regards
Nico
EDIT:
After switching my servers OS from CentOS 7 to Ubuntu 16.04 things started working.

**Tags:** cryptography, domain-registering


---

## 1 answers

### Answer by username_1 on 2018-12-05. Score: 0 | Accepted answer

When you add or alter a DNS record you need to update the serial number in the zone data and take into account the TTL (time to live) which is used by clients as a cache refresh interval. 
If you are using a hosting provider's web-based control-panel, it probably takes care of the serial number for you but it won't adjust the TTL in advance of the change. Therefore your change can take a while to propagate through third-party and client DNS caches.
NXDOMAIN means "no such domain" - so far as the nearest DNS server is concerned, it has a still-valid set of data for the parent zone and that does not contain the delegation you enquired about.
$ dig +nocmd +multiline +noall +answer machinenode.de
machinenode.de.         600 IN A 50.63.202.40

$ dig +nocmd +multiline +noall +answer dnsseed.machinenode.de
dnsseed.machinenode.de. 30 IN A 92.242.132.15

Those numbers 600 and 30 are the TTL values.

> **Comments:**
> **username_0**: Okay thanks, however I've added those records few days ago (after registering the domain)...atleast the dnsseed. one  
> **username_0**: also, if I do `dig -t NS dnsseed.machinenode.de @ns01.machinenode.de` it works fine  

---

