home/hermes
Archived
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
This repository has been archived on 2023-12-26. You can view files and clone it, but cannot push or open issues or pull requests.
20 commits 1 branch 0 tags 212 KiB
HCL 93%
Nix 4.8%
Jinja 2.2%
Find a file
Pim Kunis b5ccfd973e resolve dns.dmz to this host 
change hostname
2023-03-14 23:02:28 +01:00
.gitignore init 2023-03-11 17:10:21 +01:00
ansible.yml revert to waiting... 2023-03-13 21:52:35 +01:00
cloud_init.cfg.tftpl resolve dns.dmz to this host 2023-03-14 23:02:28 +01:00
dnsmasq.conf resolve dns.dmz to this host 2023-03-14 23:02:28 +01:00
inventory temporary fix for ansible 2023-03-12 21:21:43 +01:00
main.tf revert to waiting... 2023-03-13 21:52:35 +01:00
network_config.cfg.tftpl parameterize ip 2023-03-11 19:05:42 +01:00
README.md update readme 2023-03-13 09:36:04 +01:00
variables.tf resolve dns.dmz to this host 2023-03-14 23:02:28 +01:00

README.md

dmz-dns-vm

Provisions a VM using libvirt which acts as the DNS server on our DMZ network.

The VMs on our DMZ might like to contact eachother. For example, one VM wants to clone a repository from the git server. However, because our home network is NATed, a DNS lookup of these servers will result in our public IP address. This will in general not work, because the public IP address is only assigned on the WAN port of the router.

One solution is to overwrite DNS requests from the DMZ to the router if they query these VMs. However, then the router needs to operate on the DMZ vlan, which is not ideal in terms of security. Additionally, it would be nice to define the DNS in the DMZ in terms of infrastructure as code.

This solution creates a seperate VM on the DMZ that acts as the DNS and DHCP server. Concretely, Dnsmasq does DHCPv4 and assigns DNS names according to hostnames. Additionally, it tries to match IPv6 addresses using the SLAAC algorithm in order to incorporate them as AAAA records in DNS as well (using ra-names). Dnsmasq also overwrites the public IP address to 192.168.30.3.

What is needed from the router:

  • Static IPv4 addresses on the DMZ interface (192.168.30.1/24).
  • Static IPv6 addresses on the DMZ interface (2a02:58:19a:f730::1/64).
  • DNS domain override for geokunis2.nl, pizzapim.nl, pim.kunis.nl and dmz to 192.18.30.7.
  • unmanaged IPv6 router advertisements on the DMZ interface.