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.544 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.544/0.544/0.544/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 Tue 2024-04-09 10:00:58 UTC, end at Tue 2024-04-09 10:01:03 UTC. -- Apr 09 10:01:02 osdx dnsmasq[10861]: dnsmasq: syntax check OK. Apr 09 10:01:02 osdx dnsmasq[10868]: started, version 2.80 cachesize 150 Apr 09 10:01:02 osdx dnsmasq[10868]: DNS service limited to local subnets Apr 09 10:01:02 osdx dnsmasq[10868]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Apr 09 10:01:02 osdx dnsmasq[10868]: warning: ignoring resolv-file flag because no-resolv is set Apr 09 10:01:02 osdx dnsmasq[10868]: using nameserver 10.0.0.2#53 Apr 09 10:01:02 osdx dnsmasq[10868]: read /etc/hosts - 1 addresses Apr 09 10:01:03 osdx dnsmasq[10868]: query[A] teldat.com from ::1 Apr 09 10:01:03 osdx dnsmasq[10868]: forwarded teldat.com to 10.0.0.2 Apr 09 10:01:03 osdx dnsmasq[10868]: 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=408 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 407.516/407.516/407.516/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 Tue 2024-04-09 10:01:10 UTC, end at Tue 2024-04-09 10:01:16 UTC. -- Apr 09 10:01:13 osdx dnsmasq[11294]: dnsmasq: syntax check OK. Apr 09 10:01:13 osdx dnsmasq[11301]: started, version 2.80 cachesize 150 Apr 09 10:01:13 osdx dnsmasq[11301]: DNS service limited to local subnets Apr 09 10:01:13 osdx dnsmasq[11301]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Apr 09 10:01:13 osdx dnsmasq[11301]: warning: ignoring resolv-file flag because no-resolv is set Apr 09 10:01:13 osdx dnsmasq[11301]: using nameserver 10::2#53 Apr 09 10:01:13 osdx dnsmasq[11301]: read /etc/hosts - 1 addresses Apr 09 10:01:16 osdx dnsmasq[11301]: query[A] teldat.com from ::1 Apr 09 10:01:16 osdx dnsmasq[11301]: forwarded teldat.com to 10::2 Apr 09 10:01:16 osdx dnsmasq[11301]: 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=4.42 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.422/4.422/4.422/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 Tue 2024-04-09 10:01:22 UTC, end at Tue 2024-04-09 10:01:28 UTC. -- Apr 09 10:01:25 osdx dnsmasq[11733]: dnsmasq: syntax check OK. Apr 09 10:01:25 osdx dnsmasq[11740]: started, version 2.80 cachesize 150 Apr 09 10:01:25 osdx dnsmasq[11740]: DNS service limited to local subnets Apr 09 10:01:25 osdx dnsmasq[11740]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Apr 09 10:01:25 osdx dnsmasq[11740]: warning: ignoring resolv-file flag because no-resolv is set Apr 09 10:01:25 osdx dnsmasq[11740]: using nameserver 10.0.0.10#53 Apr 09 10:01:25 osdx dnsmasq[11740]: using nameserver 10.0.0.2#53 Apr 09 10:01:25 osdx dnsmasq[11740]: read /etc/hosts - 1 addresses Apr 09 10:01:26 osdx dnsmasq[11740]: query[A] teldat.com from ::1 Apr 09 10:01:26 osdx dnsmasq[11740]: forwarded teldat.com to 10.0.0.10 Apr 09 10:01:27 osdx dnsmasq[11740]: query[A] teldat.com from 127.0.0.1 Apr 09 10:01:28 osdx dnsmasq[11740]: query[A] teldat.com from ::1 Apr 09 10:01:28 osdx dnsmasq[11740]: forwarded teldat.com to 10.0.0.2 Apr 09 10:01:28 osdx dnsmasq[11740]: 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=405 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 405.293/405.293/405.293/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 Tue 2024-04-09 10:01:34 UTC, end at Tue 2024-04-09 10:01:42 UTC. -- Apr 09 10:01:38 osdx dnsmasq[12167]: dnsmasq: syntax check OK. Apr 09 10:01:38 osdx dnsmasq[12174]: started, version 2.80 cachesize 150 Apr 09 10:01:38 osdx dnsmasq[12174]: DNS service limited to local subnets Apr 09 10:01:38 osdx dnsmasq[12174]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Apr 09 10:01:38 osdx dnsmasq[12174]: warning: ignoring resolv-file flag because no-resolv is set Apr 09 10:01:38 osdx dnsmasq[12174]: using nameserver 10::10#53 Apr 09 10:01:38 osdx dnsmasq[12174]: using nameserver 10::2#53 Apr 09 10:01:38 osdx dnsmasq[12174]: read /etc/hosts - 1 addresses Apr 09 10:01:40 osdx dnsmasq[12174]: query[A] teldat.com from ::1 Apr 09 10:01:40 osdx dnsmasq[12174]: forwarded teldat.com to 10::10 Apr 09 10:01:41 osdx dnsmasq[12174]: query[A] teldat.com from 127.0.0.1 Apr 09 10:01:42 osdx dnsmasq[12174]: query[A] teldat.com from ::1 Apr 09 10:01:42 osdx dnsmasq[12174]: forwarded teldat.com to 10::2 Apr 09 10:01:42 osdx dnsmasq[12174]: reply teldat.com is 172.24.0.11