Dns Priority
Test suite to check DNS service priorities
Valid Address
Description
Configures a simple, valid address and checks the DNS can resolve it. There is no priority involved as a single address is in use.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.0.0.2/24 set service dns forwarding record host teldat.com ipv4-address 172.24.0.11 set service dns forwarding record host teldat.com ipv6-address ff00::dead:cafe set service dns resolver local
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10.0.0.1/24 set service dns forwarding logs set service dns resolver local set service dns forwarding name-server 10.0.0.2
Step 3: Ping IP address 10.0.0.2 from DUT0:
admin@DUT0$ ping 10.0.0.2 count 1 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.453 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.453/0.453/0.453/0.000 ms
Step 4: Run command show host lookup teldat.com type A wait 0 at DUT0 and check if output contains the following tokens:
172.24.0.11Show output
teldat.com has address 172.24.0.11
Step 5: Run command service dns forwarding show logs | cat at DUT0 and expect this output:
Show output
-- Logs begin at Wed 2024-06-12 21:47:56 UTC, end at Wed 2024-06-12 21:48:00 UTC. -- Jun 12 21:47:59 osdx dnsmasq[17341]: dnsmasq: syntax check OK. Jun 12 21:48:00 osdx dnsmasq[17348]: started, version 2.80 cachesize 150 Jun 12 21:48:00 osdx dnsmasq[17348]: DNS service limited to local subnets Jun 12 21:48:00 osdx dnsmasq[17348]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 12 21:48:00 osdx dnsmasq[17348]: warning: ignoring resolv-file flag because no-resolv is set Jun 12 21:48:00 osdx dnsmasq[17348]: using nameserver 10.0.0.2#53 Jun 12 21:48:00 osdx dnsmasq[17348]: read /etc/hosts - 1 addresses Jun 12 21:48:00 osdx dnsmasq[17348]: query[A] teldat.com from ::1 Jun 12 21:48:00 osdx dnsmasq[17348]: forwarded teldat.com to 10.0.0.2 Jun 12 21:48:00 osdx dnsmasq[17348]: reply teldat.com is 172.24.0.11
Valid Address IPv6
Description
Configures a simple, valid IPv6 address and checks the DNS can resolve it. There is no priority involved as a single address is in use.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10::2/64 set service dns forwarding record host teldat.com ipv4-address 172.24.0.11 set service dns forwarding record host teldat.com ipv6-address ff00::dead:cafe set service dns resolver local
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10::1/64 set service dns forwarding logs set service dns resolver local set service dns forwarding name-server 10::2
Step 3: Ping IP address 10::2 from DUT0:
admin@DUT0$ ping 10::2 count 1 size 56 timeout 1Show output
PING 10::2(10::2) 56 data bytes 64 bytes from 10::2: icmp_seq=1 ttl=64 time=0.546 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.546/0.546/0.546/0.000 ms
Step 4: Run command show host lookup teldat.com type A wait 0 at DUT0 and check if output contains the following tokens:
172.24.0.11Show output
teldat.com has address 172.24.0.11
Step 5: Run command service dns forwarding show logs | cat at DUT0 and expect this output:
Show output
-- Logs begin at Wed 2024-06-12 21:48:07 UTC, end at Wed 2024-06-12 21:48:12 UTC. -- Jun 12 21:48:10 osdx dnsmasq[17782]: dnsmasq: syntax check OK. Jun 12 21:48:10 osdx dnsmasq[17789]: started, version 2.80 cachesize 150 Jun 12 21:48:10 osdx dnsmasq[17789]: DNS service limited to local subnets Jun 12 21:48:10 osdx dnsmasq[17789]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 12 21:48:10 osdx dnsmasq[17789]: warning: ignoring resolv-file flag because no-resolv is set Jun 12 21:48:10 osdx dnsmasq[17789]: using nameserver 10::2#53 Jun 12 21:48:10 osdx dnsmasq[17789]: read /etc/hosts - 1 addresses Jun 12 21:48:12 osdx dnsmasq[17789]: query[A] teldat.com from ::1 Jun 12 21:48:12 osdx dnsmasq[17789]: forwarded teldat.com to 10::2 Jun 12 21:48:12 osdx dnsmasq[17789]: reply teldat.com is 172.24.0.11
Multiple Addresses
Description
Configures two DNS addresses: one invalid and the other valid. Checks that the resolution works against the second address, while the first one does not respond.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.0.0.2/24 set service dns forwarding record host teldat.com ipv4-address 172.24.0.11 set service dns forwarding record host teldat.com ipv6-address ff00::dead:cafe set service dns resolver local
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10.0.0.1/24 set service dns forwarding logs set service dns resolver local set service dns forwarding name-server 10.0.0.10 priority 0 set service dns forwarding name-server 10.0.0.2 priority 1
Step 3: Ping IP address 10.0.0.2 from DUT0:
admin@DUT0$ ping 10.0.0.2 count 1 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.634 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.634/0.634/0.634/0.000 ms
Step 4: Run command show host lookup teldat.com type A wait 0 at DUT0 and check if output contains the following tokens:
172.24.0.11Show output
teldat.com has address 172.24.0.11
Step 5: Run command service dns forwarding show logs | cat at DUT0 and expect this output:
Show output
-- Logs begin at Wed 2024-06-12 21:48:19 UTC, end at Wed 2024-06-12 21:48:25 UTC. -- Jun 12 21:48:23 osdx dnsmasq[18221]: dnsmasq: syntax check OK. Jun 12 21:48:23 osdx dnsmasq[18228]: started, version 2.80 cachesize 150 Jun 12 21:48:23 osdx dnsmasq[18228]: DNS service limited to local subnets Jun 12 21:48:23 osdx dnsmasq[18228]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 12 21:48:23 osdx dnsmasq[18228]: warning: ignoring resolv-file flag because no-resolv is set Jun 12 21:48:23 osdx dnsmasq[18228]: using nameserver 10.0.0.10#53 Jun 12 21:48:23 osdx dnsmasq[18228]: using nameserver 10.0.0.2#53 Jun 12 21:48:23 osdx dnsmasq[18228]: read /etc/hosts - 1 addresses Jun 12 21:48:23 osdx dnsmasq[18228]: query[A] teldat.com from ::1 Jun 12 21:48:23 osdx dnsmasq[18228]: forwarded teldat.com to 10.0.0.10 Jun 12 21:48:24 osdx dnsmasq[18228]: query[A] teldat.com from 127.0.0.1 Jun 12 21:48:25 osdx dnsmasq[18228]: query[A] teldat.com from ::1 Jun 12 21:48:25 osdx dnsmasq[18228]: forwarded teldat.com to 10.0.0.2 Jun 12 21:48:25 osdx dnsmasq[18228]: reply teldat.com is 172.24.0.11
Multiple IPv6 Addresses
Description
Configures two IPv6 DNS addresses: one invalid and the other valid. Checks that the resolution works against the second address, while the first one does not respond.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10::2/64 set service dns forwarding record host teldat.com ipv4-address 172.24.0.11 set service dns forwarding record host teldat.com ipv6-address ff00::dead:cafe set service dns resolver local
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10::1/64 set service dns forwarding logs set service dns resolver local set service dns forwarding name-server 10::10 priority 0 set service dns forwarding name-server 10::2 priority 1
Step 3: Ping IP address 10::2 from DUT0:
admin@DUT0$ ping 10::2 count 1 size 56 timeout 1Show output
PING 10::2(10::2) 56 data bytes 64 bytes from 10::2: icmp_seq=1 ttl=64 time=0.554 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.554/0.554/0.554/0.000 ms
Step 4: Run command show host lookup teldat.com type A wait 0 at DUT0 and check if output contains the following tokens:
172.24.0.11Show output
teldat.com has address 172.24.0.11
Step 5: Run command service dns forwarding show logs | cat at DUT0 and expect this output:
Show output
-- Logs begin at Wed 2024-06-12 21:48:31 UTC, end at Wed 2024-06-12 21:48:39 UTC. -- Jun 12 21:48:35 osdx dnsmasq[18657]: dnsmasq: syntax check OK. Jun 12 21:48:35 osdx dnsmasq[18664]: started, version 2.80 cachesize 150 Jun 12 21:48:35 osdx dnsmasq[18664]: DNS service limited to local subnets Jun 12 21:48:35 osdx dnsmasq[18664]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 12 21:48:35 osdx dnsmasq[18664]: warning: ignoring resolv-file flag because no-resolv is set Jun 12 21:48:35 osdx dnsmasq[18664]: using nameserver 10::10#53 Jun 12 21:48:35 osdx dnsmasq[18664]: using nameserver 10::2#53 Jun 12 21:48:35 osdx dnsmasq[18664]: read /etc/hosts - 1 addresses Jun 12 21:48:37 osdx dnsmasq[18664]: query[A] teldat.com from ::1 Jun 12 21:48:37 osdx dnsmasq[18664]: forwarded teldat.com to 10::10 Jun 12 21:48:38 osdx dnsmasq[18664]: query[A] teldat.com from 127.0.0.1 Jun 12 21:48:39 osdx dnsmasq[18664]: query[A] teldat.com from ::1 Jun 12 21:48:39 osdx dnsmasq[18664]: forwarded teldat.com to 10::2 Jun 12 21:48:39 osdx dnsmasq[18664]: reply teldat.com is 172.24.0.11