Domain names, domain nameservers, DNS and DHCP

Domain names, Domain nameservers, DNS and DHCP are a key part of the internet back bone.

• DNS (Domain Name System) resolves the text domain names to the relevant IP (Internet Protocol) addresses.
• DHCP (Dynamic Host Configuration Protocol) allows the automatic assignment of IP addresses to hardware via a MAC (Medium Access Control) address, sometime domain names are also assigned.
• IPv4 used a broadcast system for ARP (Address Resolution Protocol)
• IPv6 assigns a link-local address to every network interface. It then uses the link local addresses with neighbor discovery for global IP addressing, with a DHCP or Router Advertisements.
• Each hardware connection point has an associated MAC number to which one or more IP addresses can be assigned
  • Unmanaged switches only use tables of the source attached MAC number of the related connected ports for communication.
    • An unmanaged switch does not normally have its own MAC number nor IP address.
    • It builds a table of source MAC numbers for each port, which it change then use for addressing purposes.
    • A port can have multiple source MAC numbers, such when it is attached to another unmanaged switch.
    • An unmanaged switch can not transfer data between VLANs (Virtual Local Area Network). It can transfer data on the same VLAN domain.
  • Managed switches have a MAC number
    • Managed switches usually have an assigned IP address for management access associated with the switch MAC number. (It may be possible that is a separate out of band management port, usually Ethernet, but can be serial port type)
    • Managed switches can be Level 2 only, which allows VLANs to be managed and routed between ports.
    • Managed switches can be Level 3, which allows IP routing as well as VLANs to function. The IP routing functions are often limited, that is not all IP router functions are available on Level 3 switches.
    • The exact management functionality of managed switches varies and not all features maybe available on every model of switch. In fact functionality of managed switches can be expected to vary considerably between models.
• domain names are the text used to identify internet resources. The are registered with a domain name registrar.
• domain nameservers are used to assign IP addresses as well as other information to a domain name.

There are a number of levels of DNS, the system interrogates in the following order:

1. host file, this is a basic file on each computer operating system
   1. The usual automatic entries are:
      1. The local machine host name and ip address
      2. The loop back address
2. Additional manual entries can be added for any host name and IP address. (This can be hand on occassions, such as setting up VPNs where the setup process changes internet access for DNS stop working. The host file manual can still allow address resolution.
3. local dns resolver
   1. machine based
      1. many operating systems have a local caching DNS server installed to improve DNS performance.
   2. LAN based
      1. This can act as a local caching DNS server and also be used for LAN
4. public resolver
5. authoritative domain resolver

1. Quad9, free no commercial foundation
   1. IPv4 (filtered)
      1. 9.9.9.9
      2. 149.112.112.112
   2. IPv6 (filtered)
      1. 2620:fe::fe
      2. 2620:fe::9
2. OpenDNS, belongs to Cisco
   1. IPv4 (filtered)
      1. 208.67.222.123
      2. 208.67.220.123
   2. IPv6 (filtered)
      1. 2620:119:35::35
      2. 2620:119:53::53
   3. IPv6 (unfiltered)
      1. 2620:0:ccc::2
      2. 2620:0:ccd::2
3. one.one.one.one (Cloudflare)
   1. IPv4 (unfiltered)
      1. 1.1.1.1
      2. 1.0.0.1
   2. IPv6 (unfiltered)
      1. 2620:4700:4700::1111
      2. 2620:4700:4700::1001
   3. See one.one.one.one/family for filtered options

The local OS DNS servers are specified in /etc/resolv.conf

The bind9 file that configs the DNS forwarders is /etc/bind/name.conf.options, the DNS forwarders are configured.

The kea dhcp configuration has the following related to DNS and gateway setup.

dhcpv4.conf

  "subnet4": [
    {
      "subnet": "192.168.1.0/24",
 
      // There are no relays in this network, so we need to tell Kea that this subnet
      // is reachable directly via the specified interface.
      "interface": "enp1s0",
 
     "pools": [
        {
          "pool": "192.168.1.100 - 192.168.1.200"
        }
      ],
    "option-data": [
      {
        "name": "routers",
        "data": "192.168.1.1"
      },
      {
        "name": "domain-name-servers",
        "data": "192.168.1.14,192.168.1.2,9.9.9.9"
      }
    ],