Exercise 2: Debian Client in the LAN Segment

Building on the srv1 DNS server setup, add a second VM acting as a client on the same LAN segment and verify that it can resolve names via srv1.

1. System Requirements & Network

Set up a second Linux VM as a Debian 13 (Trixie) minimal installation (no GUI).

Hostname: client1
Network interfaces: The VM must have two network cards.
- Interface 1 (WAN): Dynamic IP address via DHCP (NAT).
- Interface 2 (LAN): Attached to the same host-only network as srv1. Static IPv4 address within the 172.30.0.0/16 range, distinct from 172.30.0.1 (e.g. 172.30.0.2/16).
Protocol restriction: IPv4 only — IPv6 must be deactivated/unused on the interfaces, same as on srv1.
DNS resolver: client1 must use srv1 (172.30.0.1) as its nameserver for lookups.
Client DNS entry: client1 must be added to the DNS configuration aswell, to enable both forward and backup lookups.

Test and document the following from client1:

Connectivity: Confirm client1 can reach srv1 over the LAN segment (e.g. ping 172.30.0.1).
Forward resolution: Resolve srv1.mydomain.intern and ns1.mydomain.intern using both dig and nslookup.
Reverse lookup: Resolve 172.30.0.1 back to its hostname using dig -x and nslookup.
Forwarder: Resolve an external name (e.g. google.com) and confirm the query was actually served by srv1 (172.30.0.1), not by some other resolver.
Client lookup: Resolve client1.mydomain.intern and its assigned IP (e.g. 172.30.0.2) with dig from both srv1 and client1
IPv4-only: Confirm neither interface of client1 has an IPv6 address assigned.