447 Networking: Difference between revisions

From London Hackspace Wiki

m
→‎DNS: removed babbage reference and improved wording and internal links.
No edit summary
m (→‎DNS: removed babbage reference and improved wording and internal links.)
Line 35: Line 35:
== DNS ==
== DNS ==


boole runs bind as a nameserver and unbound as a caching resolver, they run on different ip's, it has to be done this way to make DNSSEC work.
[[Boole]] runs BIND as a nameserver and unbound as a caching resolver, they run on different IP addresses, it has to be done this way to make DNSSEC work.


The dhcp server pokes hostnames that the dhcp clients send it into dns under '''dhcp.lan.london.hackspace.org.uk'''. The default search path is '''lan.london.hackspace.org.uk''', so if you want to lookup a hostname for a machine that is a dhcp client, e.g. '''fish''' then you'd lookup '''fish.dhcp''', this avoids problems with dhcp clients asking to be '''wpad''' etc...
The DHCP server registers hostnames that the DHCP clients send it into dns under '''dhcp.lan.london.hackspace.org.uk'''. The default search path is '''lan.london.hackspace.org.uk''', so if a client wants to lookup a hostname for a machine that is a DHCP client, e.g. '''fish''' then it would lookup '''fish.dhcp''', this configuration avoids problems with DHCP clients asking to be '''wpad''' etc...


machines with static ip's are just under '''lan.london.hackspace.org.uk''', so you can go straight to '''babbage''', '''tesla''', etc...
Machines with static IP addresses use the subdomain '''lan.london.hackspace.org.uk''', so you can go straight to hosts '''chomsky''', '''tesla''', etc...


to flush the unbound cache run (as root, on boole):
To flush the unbound cache run (with root privileges, on [[boole]]):


  unbound-control flush_zone dhcp.lan.london.hackspace.org.uk
  unbound-control flush_zone dhcp.lan.london.hackspace.org.uk