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.705 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.705/0.705/0.705/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 Mon 2024-06-24 12:34:27 UTC, end at Mon 2024-06-24 12:34:31 UTC. -- Jun 24 12:34:30 osdx dnsmasq[30413]: dnsmasq: syntax check OK. Jun 24 12:34:30 osdx dnsmasq[30420]: started, version 2.80 cachesize 150 Jun 24 12:34:30 osdx dnsmasq[30420]: DNS service limited to local subnets Jun 24 12:34:30 osdx dnsmasq[30420]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 24 12:34:30 osdx dnsmasq[30420]: warning: ignoring resolv-file flag because no-resolv is set Jun 24 12:34:30 osdx dnsmasq[30420]: using nameserver 10.0.0.2#53 Jun 24 12:34:30 osdx dnsmasq[30420]: read /etc/hosts - 1 addresses Jun 24 12:34:31 osdx dnsmasq[30420]: query[A] teldat.com from ::1 Jun 24 12:34:31 osdx dnsmasq[30420]: forwarded teldat.com to 10.0.0.2 Jun 24 12:34:31 osdx dnsmasq[30420]: 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.519 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.519/0.519/0.519/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 Mon 2024-06-24 12:34:36 UTC, end at Mon 2024-06-24 12:34:42 UTC. -- Jun 24 12:34:39 osdx dnsmasq[30848]: dnsmasq: syntax check OK. Jun 24 12:34:39 osdx dnsmasq[30855]: started, version 2.80 cachesize 150 Jun 24 12:34:39 osdx dnsmasq[30855]: DNS service limited to local subnets Jun 24 12:34:39 osdx dnsmasq[30855]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 24 12:34:39 osdx dnsmasq[30855]: warning: ignoring resolv-file flag because no-resolv is set Jun 24 12:34:39 osdx dnsmasq[30855]: using nameserver 10::2#53 Jun 24 12:34:39 osdx dnsmasq[30855]: read /etc/hosts - 1 addresses Jun 24 12:34:41 osdx dnsmasq[30855]: query[A] teldat.com from ::1 Jun 24 12:34:41 osdx dnsmasq[30855]: forwarded teldat.com to 10::2 Jun 24 12:34:42 osdx dnsmasq[30855]: 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.510 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.510/0.510/0.510/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 Mon 2024-06-24 12:34:48 UTC, end at Mon 2024-06-24 12:34:54 UTC. -- Jun 24 12:34:51 osdx dnsmasq[31287]: dnsmasq: syntax check OK. Jun 24 12:34:51 osdx dnsmasq[31294]: started, version 2.80 cachesize 150 Jun 24 12:34:51 osdx dnsmasq[31294]: DNS service limited to local subnets Jun 24 12:34:51 osdx dnsmasq[31294]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 24 12:34:51 osdx dnsmasq[31294]: warning: ignoring resolv-file flag because no-resolv is set Jun 24 12:34:51 osdx dnsmasq[31294]: using nameserver 10.0.0.10#53 Jun 24 12:34:51 osdx dnsmasq[31294]: using nameserver 10.0.0.2#53 Jun 24 12:34:51 osdx dnsmasq[31294]: read /etc/hosts - 1 addresses Jun 24 12:34:52 osdx dnsmasq[31294]: query[A] teldat.com from ::1 Jun 24 12:34:52 osdx dnsmasq[31294]: forwarded teldat.com to 10.0.0.10 Jun 24 12:34:53 osdx dnsmasq[31294]: query[A] teldat.com from 127.0.0.1 Jun 24 12:34:54 osdx dnsmasq[31294]: query[A] teldat.com from ::1 Jun 24 12:34:54 osdx dnsmasq[31294]: forwarded teldat.com to 10.0.0.2 Jun 24 12:34:54 osdx dnsmasq[31294]: 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=421 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 420.633/420.633/420.633/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 Mon 2024-06-24 12:35:00 UTC, end at Mon 2024-06-24 12:35:08 UTC. -- Jun 24 12:35:03 osdx dnsmasq[31728]: dnsmasq: syntax check OK. Jun 24 12:35:03 osdx dnsmasq[31735]: started, version 2.80 cachesize 150 Jun 24 12:35:03 osdx dnsmasq[31735]: DNS service limited to local subnets Jun 24 12:35:03 osdx dnsmasq[31735]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Jun 24 12:35:03 osdx dnsmasq[31735]: warning: ignoring resolv-file flag because no-resolv is set Jun 24 12:35:03 osdx dnsmasq[31735]: using nameserver 10::10#53 Jun 24 12:35:03 osdx dnsmasq[31735]: using nameserver 10::2#53 Jun 24 12:35:03 osdx dnsmasq[31735]: read /etc/hosts - 1 addresses Jun 24 12:35:06 osdx dnsmasq[31735]: query[A] teldat.com from ::1 Jun 24 12:35:06 osdx dnsmasq[31735]: forwarded teldat.com to 10::10 Jun 24 12:35:07 osdx dnsmasq[31735]: query[A] teldat.com from 127.0.0.1 Jun 24 12:35:08 osdx dnsmasq[31735]: query[A] teldat.com from ::1 Jun 24 12:35:08 osdx dnsmasq[31735]: forwarded teldat.com to 10::2 Jun 24 12:35:08 osdx dnsmasq[31735]: reply teldat.com is 172.24.0.11