Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| router:dhcp-dns [2024/08/26 09:19] – willy | router:dhcp-dns [2025/02/06 08:03] (current) – removed willy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== DNS, DHCP and routing for the internal network ===== | ||
| - | |||
| - | Since your home network is connected **only** to your home server (right?), in order to be able to navigate and use the home network you must configure some services on your home server. | ||
| - | |||
| - | In detail, you will need: | ||
| - | * one DNS server, so that devices in the home network can resolve names to addresses (and filter ads) | ||
| - | * one DHCP server, so provide devices in the home network with automatic configuration | ||
| - | * one default gateway and router: to allow devices in the home network to access stuff on the internet | ||
| - | |||
| - | At first i have been using DNSmasq, which is a seemingly easy approach to both DNS and DHCP for the home network. After a lengthly and annoying debugging session with Android devices i found out that DNS has evolved a lot and DNSMasq is today a bit outdated. | ||
| - | |||
| - | I decided then to go straight to the Gentoo standard DHCP server and Unbound DNS resolver/ | ||
| - | |||
| - | For future reference, the older DNSMasq information has been moved to a separate page. | ||
| - | |||
| - | To create a router, you will be using the Linux built-in great nftables tools that today has replaced the older iptables. | ||
| - | |||
| - | |||
| - | === Unbound, your very own DNS resolver === | ||
| - | |||
| - | [[https:// | ||
| - | |||
| - | [[https:// | ||
| - | |||
| - | It's very simple to setup on Gentoo (see [[https:// | ||
| - | |||
| - | So, first of all emerge Unbound: | ||
| - | <code bash> | ||
| - | emerge unbound | ||
| - | </ | ||
| - | |||
| - | I am using the following **/ | ||
| - | <file - unbound.conf> | ||
| - | server: | ||
| - | verbosity: 1 | ||
| - | num-threads: | ||
| - | interface: 10.0.0.1 | ||
| - | interface: 127.0.0.1 | ||
| - | port: 53 | ||
| - | so-reuseport: | ||
| - | cache-min-ttl: | ||
| - | cache-max-ttl: | ||
| - | do-ip4: yes | ||
| - | do-ip6: yes | ||
| - | do-udp: yes | ||
| - | do-tcp: yes | ||
| - | use-systemd: | ||
| - | do-daemonize: | ||
| - | # For security reasons, only clients on the home interface can use the DNS service | ||
| - | | ||
| - | access-control: | ||
| - | use-syslog: yes | ||
| - | hide-identity: | ||
| - | hide-version: | ||
| - | harden-short-bufsize: | ||
| - | harden-large-queries: | ||
| - | harden-glue: | ||
| - | harden-dnssec-stripped: | ||
| - | harden-below-nxdomain: | ||
| - | harden-referral-path: | ||
| - | harden-algo-downgrade: | ||
| - | qname-minimisation: | ||
| - | qname-minimisation-strict: | ||
| - | aggressive-nsec: | ||
| - | use-caps-for-id: | ||
| - | prefetch: yes | ||
| - | rrset-roundrobin: | ||
| - | minimal-responses: | ||
| - | # This will enable DoT (upstream) | ||
| - | tls-cert-bundle: | ||
| - | # This will add Ad blocking | ||
| - | include: / | ||
| - | # Add a local resolve for the home server | ||
| - | local-zone: " | ||
| - | local-data: " | ||
| - | |||
| - | remote-control: | ||
| - | control-enable: | ||
| - | |||
| - | forward-zone: | ||
| - | name: " | ||
| - | # Use Google DNS as upstream DNS (put here your preferred ones if not Google) | ||
| - | forward-tls-upstream: | ||
| - | forward-addr: | ||
| - | forward-addr: | ||
| - | </ | ||
| - | |||
| - | This is the default Gentoo unbound configuration with a few changes here and there. | ||
| - | |||
| - | At this point, read the [[router: | ||
| - | |||
| - | You need to populate your **/ | ||
| - | <file - resolv.conf> | ||
| - | # My own local DNS resolver (Unbound) | ||
| - | nameserver 127.0.0.1 | ||
| - | </ | ||
| - | |||
| - | Don't forget to autostart Unbound service: | ||
| - | <code bash> | ||
| - | rc-update add unbound default | ||
| - | / | ||
| - | </ | ||
| - | |||
| - | |||
| - | |||
| - | ==== DNSMasq ==== | ||
| - | |||
| - | Installing DNSMasq is easy enough, but better enable a couple of specific use flags first: | ||
| - | <code bash> | ||
| - | > echo net-dns/ | ||
| - | </ | ||
| - | |||
| - | **dhcp-tools** is needed to ensure dnsmasq will support DHCP, while **dnssec** will be useful to enable dnssec support on the home network. | ||
| - | |||
| - | Install the tool: | ||
| - | <code bash> | ||
| - | > emerge dnsmasq | ||
| - | </ | ||
| - | |||
| - | All you actually need to do it create a meaningful configuration file, take this one as example: | ||
| - | <file - dnsmasq.conf> | ||
| - | # Here put your home LAN interface | ||
| - | listen-address=10.0.0.1 | ||
| - | bind-interfaces | ||
| - | # do not resolve your internal DNS names outside | ||
| - | domain-needed | ||
| - | # Never forward addresses in the non-routed address spaces | ||
| - | bogus-priv | ||
| - | # Enable dnssec support | ||
| - | # | ||
| - | #dnssec | ||
| - | # | ||
| - | # You can add your own ads filters here (only hosts format!) | ||
| - | # | ||
| - | # Use this custom-folder to add more blocklists; | ||
| - | # conf-dir=/ | ||
| - | # DHCP settings for internal network (from 100 to 250, under 100 are fixed ips) | ||
| - | dhcp-range=10.0.0.100, | ||
| - | # Send gateway and DNS values to the DHCP clients | ||
| - | dhcp-option=option: | ||
| - | dhcp-option=option: | ||
| - | # Preassign fixed IPs via DHCP to specific hosts: | ||
| - | # | ||
| - | # DNSSEC | ||
| - | conf-file=/ | ||
| - | dnssec | ||
| - | dnssec-check-unsigned | ||
| - | </ | ||
| - | |||
| - | Dnsmasq will operate **only** on your internal network by listening only on 10.0.0.1 IP address and being bind-ed to the associated interface. This is specially needed if you are using Unbound as DNS resolver. | ||
| - | |||
| - | Here i assign a pool od dynamic IP addresses (from 100 to 254) on the 10.0.0.0 subnet. Addresses under 100 can be used for static assignments. For example, i use static IPs for all my OpenWRT Access Points and wired security cameras, and dynamic for all other devices. | ||
| - | |||
| - | To be sure that all devices will use the home server both as DNS server and gateway, you need to set the two above dhcp options. This will not work for devices that use hard-coded DNS servers (like Fire Sticks and Google Chromecasts...) but there is a workaround for those too, and i will show you later on. | ||
| - | |||
| - | Well, this is almost all. Start //dnsmasq// service and make it start on boot: | ||
| - | <code bash> | ||
| - | > rc-update add dnsmasq default | ||
| - | > / | ||
| - | </ | ||
| - | |||
| - | Now you can connect your devices to the home network and they will get an IP address and a full network configuration to go with it. | ||
| - | |||
| - | |||
| - | ==== Hosts file ==== | ||
| - | |||
| - | DNSMasq will use your home server **/ | ||
| - | <file - hosts> | ||
| - | 10.0.0.1 home.mydomain.com | ||
| - | 10.0.0.1 mydomain.com | ||
| - | </ | ||
| - | |||
| - | So that all devices inside your network will be able to reach your internal services like they are from outside, and mobile devices will only require **one** configuration both when they are inside and outside your home network. | ||