Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tech_notes:dns [2024-05-18 Sat wk20 15:38] – baumkp | tech_notes:dns [2025-08-09 Sat wk32 11:11] (current) – [Public DNS providers] baumkp | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Domain names, domain nameservers, | ======Domain names, domain nameservers, | ||
| Domain names, Domain nameservers, | Domain names, Domain nameservers, | ||
| - | *DNS resolves the text domain names to the relevant | + | *DNS (Domain Name System) |
| - | *DHCP allows the automatic assignment of ip addresses to hardware | + | *DHCP (Dynamic Host Configuration Protocol) |
| + | *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 | *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. | *Unmanaged switches only use tables of the source attached MAC number of the related connected ports for communication. | ||
| Line 8: | Line 10: | ||
| *It builds a table of source MAC numbers for each port, which it change then use for addressing purposes. | *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. | *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. It can transfer data on the same VLAN domain. | + | *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 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 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) | ||
| Line 14: | Line 16: | ||
| *Managed switches can be Level 3, which allows IP routing as well as VLANs to function. | *Managed switches can be Level 3, which allows IP routing as well as VLANs to function. | ||
| *The exact management functionality of managed switches varies and not all features maybe available on every model of switch. | *The exact management functionality of managed switches varies and not all features maybe available on every model of switch. | ||
| - | *domain names are the text used to identify | + | *domain names are the text used to identify internet resources. |
| - | *domain nameservers are used to assign | + | *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. | + | There are a number of levels of DNS, the system interrogates in the following order: |
| - | - host file, this is a basic file on each computer where | + | - host file, this is a basic file on each computer |
| + | -The usual automatic entries are: | ||
| + | -The local machine host name and ip address | ||
| + | -The loop back address | ||
| + | - Additional manual entries can be added for any host name and IP address. | ||
| - local dns resolver | - local dns resolver | ||
| - machine based | - machine based | ||
| + | - many operating systems have a local caching DNS server installed to improve DNS performance. | ||
| - LAN based | - LAN based | ||
| - | | + | |
| + | - public | ||
| - authoritative domain resolver | - authoritative domain resolver | ||
| + | =====Public DNS providers===== | ||
| + | - [[https:// | ||
| + | - IPv4 (filtered) | ||
| + | - 9.9.9.9 | ||
| + | - 149.112.112.112 | ||
| + | - IPv6 (filtered) | ||
| + | - 2620:fe::fe | ||
| + | - 2620:fe::9 | ||
| + | - [[https:// | ||
| + | - [[https:// | ||
| + | - IPv4 | ||
| + | - 208.67.222.222 | ||
| + | - 208.67.220.220 | ||
| + | - IPv4 (filtered family shield, not-configurable) | ||
| + | - 208.67.222.123 | ||
| + | - 208.67.220.123 | ||
| + | - IPv6 (filtered) | ||
| + | - 2620: | ||
| + | - 2620: | ||
| + | - IPv6 (unfiltered) | ||
| + | - 2620: | ||
| + | - 2620: | ||
| + | - [[https:// | ||
| + | - IPv4 (unfiltered) | ||
| + | - 1.1.1.1 | ||
| + | - 1.0.0.1 | ||
| + | - IPv6 (unfiltered) | ||
| + | - 2620: | ||
| + | - 2620: | ||
| + | - See [[https:// | ||
| + | - [[https:// | ||
| + | - IPv4 (unfiltered) | ||
| + | - 8.8.8.8 | ||
| + | - 8.8.4.4 | ||
| + | - IPv6 (unfiltered) | ||
| + | - 2001: | ||
| + | - 2001: | ||
| + | =====Linux DNS Setup===== | ||
| + | The local OS DNS servers are specified in ''/ | ||
| + | The bind9 file that configs the DNS forwarders is ''/ | ||
| + | ++++/ | ||
| + | < | ||
| + | //quad9 with basic malware blocking, no ECS | ||
| + | 9.9.9.9; | ||
| + | 149.112.112.112; | ||
| + | // | ||
| + | //1.1.1.1; | ||
| + | //1.0.0.1; | ||
| + | // | ||
| + | 1.1.1.2; | ||
| + | 1.0.0.2; | ||
| + | //Opendns basic | ||
| + | 208.67.222.222; | ||
| + | 208.67.220.220; | ||
| + | };</ | ||
| + | ++++ | ||
| + | |||
| + | The kea dhcp configuration has the following related to DNS and gateway setup. | ||
| + | ++++dhcpv4.conf| | ||
| + | <code yaml> | ||
| + | { | ||
| + | " | ||
| + | |||
| + | // There are no relays in this network, so we need to tell Kea that this subnet | ||
| + | // is reachable directly via the specified interface. | ||
| + | " | ||
| + | |||
| + | " | ||
| + | { | ||
| + | " | ||
| + | } | ||
| + | ], | ||
| + | " | ||
| + | { | ||
| + | " | ||
| + | " | ||
| + | }, | ||
| + | { | ||
| + | " | ||
| + | " | ||
| + | } | ||
| + | ],</ | ||
| + | ++++ | ||
| + | |||
| + | =====DNS Performance Checker===== | ||
| + | A good resource for checking DNS performance is from [[https:// | ||
| + | When run on 2025-08-09 basic performance rankings with average cached response times are: | ||
| + | 1. QUAD9-AS-1, US (3ms) | ||
| + | 1. CLOUDFLARENET, | ||
| + | 2. CISCO-UMBRELLA, | ||
| + | 3. GOGGLE, US (47ms) | ||
| <- tech_notes: | <- tech_notes: | ||