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=3.97 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.971/3.971/3.971/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-12-02 20:31:51 UTC, end at Mon 2024-12-02 20:31:56 UTC. -- Dec 02 20:31:55 osdx dnsmasq[18269]: dnsmasq: syntax check OK. Dec 02 20:31:55 osdx dnsmasq[18276]: started, version 2.80 cachesize 150 Dec 02 20:31:55 osdx dnsmasq[18276]: DNS service limited to local subnets Dec 02 20:31:55 osdx dnsmasq[18276]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Dec 02 20:31:55 osdx dnsmasq[18276]: warning: ignoring resolv-file flag because no-resolv is set Dec 02 20:31:55 osdx dnsmasq[18276]: using nameserver 10.0.0.2#53 Dec 02 20:31:55 osdx dnsmasq[18276]: read /etc/hosts - 1 addresses Dec 02 20:31:56 osdx dnsmasq[18276]: query[A] teldat.com from ::1 Dec 02 20:31:56 osdx dnsmasq[18276]: forwarded teldat.com to 10.0.0.2 Dec 02 20:31:56 osdx dnsmasq[18276]: 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=377 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 377.134/377.134/377.134/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-12-02 20:32:02 UTC, end at Mon 2024-12-02 20:32:10 UTC. -- Dec 02 20:32:07 osdx dnsmasq[18735]: dnsmasq: syntax check OK. Dec 02 20:32:07 osdx dnsmasq[18742]: started, version 2.80 cachesize 150 Dec 02 20:32:07 osdx dnsmasq[18742]: DNS service limited to local subnets Dec 02 20:32:07 osdx dnsmasq[18742]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Dec 02 20:32:07 osdx dnsmasq[18742]: warning: ignoring resolv-file flag because no-resolv is set Dec 02 20:32:07 osdx dnsmasq[18742]: using nameserver 10::2#53 Dec 02 20:32:07 osdx dnsmasq[18742]: read /etc/hosts - 1 addresses Dec 02 20:32:10 osdx dnsmasq[18742]: query[A] teldat.com from ::1 Dec 02 20:32:10 osdx dnsmasq[18742]: forwarded teldat.com to 10::2 Dec 02 20:32:10 osdx dnsmasq[18742]: 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=12.3 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 12.266/12.266/12.266/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-12-02 20:32:19 UTC, end at Mon 2024-12-02 20:32:27 UTC. -- Dec 02 20:32:24 osdx dnsmasq[19199]: dnsmasq: syntax check OK. Dec 02 20:32:24 osdx dnsmasq[19206]: started, version 2.80 cachesize 150 Dec 02 20:32:24 osdx dnsmasq[19206]: DNS service limited to local subnets Dec 02 20:32:24 osdx dnsmasq[19206]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Dec 02 20:32:24 osdx dnsmasq[19206]: warning: ignoring resolv-file flag because no-resolv is set Dec 02 20:32:24 osdx dnsmasq[19206]: using nameserver 10.0.0.10#53 Dec 02 20:32:24 osdx dnsmasq[19206]: using nameserver 10.0.0.2#53 Dec 02 20:32:24 osdx dnsmasq[19206]: read /etc/hosts - 1 addresses Dec 02 20:32:25 osdx dnsmasq[19206]: query[A] teldat.com from ::1 Dec 02 20:32:25 osdx dnsmasq[19206]: forwarded teldat.com to 10.0.0.10 Dec 02 20:32:26 osdx dnsmasq[19206]: query[A] teldat.com from 127.0.0.1 Dec 02 20:32:27 osdx dnsmasq[19206]: query[A] teldat.com from ::1 Dec 02 20:32:27 osdx dnsmasq[19206]: forwarded teldat.com to 10.0.0.2 Dec 02 20:32:27 osdx dnsmasq[19206]: 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.468 ms --- 10::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.468/0.468/0.468/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-12-02 20:32:33 UTC, end at Mon 2024-12-02 20:32:41 UTC. -- Dec 02 20:32:37 osdx dnsmasq[19662]: dnsmasq: syntax check OK. Dec 02 20:32:37 osdx dnsmasq[19669]: started, version 2.80 cachesize 150 Dec 02 20:32:37 osdx dnsmasq[19669]: DNS service limited to local subnets Dec 02 20:32:37 osdx dnsmasq[19669]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Dec 02 20:32:37 osdx dnsmasq[19669]: warning: ignoring resolv-file flag because no-resolv is set Dec 02 20:32:37 osdx dnsmasq[19669]: using nameserver 10::10#53 Dec 02 20:32:37 osdx dnsmasq[19669]: using nameserver 10::2#53 Dec 02 20:32:37 osdx dnsmasq[19669]: read /etc/hosts - 1 addresses Dec 02 20:32:39 osdx dnsmasq[19669]: query[A] teldat.com from ::1 Dec 02 20:32:39 osdx dnsmasq[19669]: forwarded teldat.com to 10::10 Dec 02 20:32:40 osdx dnsmasq[19669]: query[A] teldat.com from 127.0.0.1 Dec 02 20:32:41 osdx dnsmasq[19669]: query[A] teldat.com from ::1 Dec 02 20:32:41 osdx dnsmasq[19669]: forwarded teldat.com to 10::2 Dec 02 20:32:41 osdx dnsmasq[19669]: reply teldat.com is 172.24.0.11