Revision as of 13:00, 14 February 2019

Nurdspace DNS

We have two different DNS views in place. The first, the external view, is used by the internet to resolve our externally configured domains. The second view is a much more elaborate view on our internal network.

Internal DNS

Our internal nameserver is based on Bind9 which is running on nurdservices. This host is configured as the authoritative (primary) server for the domains specified below:

space.nurdspace.nl
ldap.nurdspace.nl
ldap.nurd.space
git.nurd.space
saml.nurd.space
portal.nurdspace.nl
spacevpn
vm.nurd.space
lan.nurd.space
router.nurd.space
guest.nurd.space
management.nurd.space
dhcp.nurd.space
30.172.in-addr.arpa
42.208.10.in-addr.arpa
43.208.10.in-addr.arpa
30.208.10.in-addr.arpa
11.208.10.in-addr.arpa
0.31.172.in-addr.arpa
250.31.172.in-addr.arpa
c.9.a.7.0.7.4.0.1.0.0.2.ip6.arpa
ti
20.0.10.in-addr.arpa
21.0.10.in-addr.arpa
22.0.10.in-addr.arpa
space.sk1llz.nl
100.10.in-addr.arpa

Tips & Tricks

We use cached zonefiles on this system. This can mean that, during a reload of a zonefile, the file is not reloaded, because the cache is not cleared. To fix this, delete all files ending with .jnl and restart bind, eg:

# rm -f /etc/bind/zones/*.jnl
# systemctl restart bind9

External DNS

Configured zones:

nurdspace.nl

@@ Line 31: / Line 31: @@
 * space.sk1llz.nl
 * 100.10.in-addr.arpa
+=== Tips & Tricks ===
+We use cached zonefiles on this system. This can mean that, during a reload of a zonefile, the file is not reloaded, because the cache is not cleared. To fix this, delete all files ending with .jnl and restart bind, eg:
+<pre>
+# rm -f /etc/bind/zones/*.jnl
+# systemctl restart bind9
+</pre>
 == External DNS ==
 Configured zones:
 * nurdspace.nl