-
Notifications
You must be signed in to change notification settings - Fork 26
Description
In some cases, such as in https://zonemaster.net/result/736301faccbc555c, one or several messages contains a long list of IP addresses or name server name and IP address pairs. The lists makes it harder to read the message. An example from the test in the link above is the following message from DNSSEC10.
The zone has NSEC records. Fetched from the nameservers with IP addresses "192.112.36.4; 192.203.230.10; 192.33.4.12; 192.36.148.17; 192.5.5.241; 193.0.14.129; 198.41.0.4; 198.97.190.53; 199.7.83.42; 199.7.91.13; 199.9.14.201; 2001:500:12::d0d; 2001:500:1::53; 2001:500:200::b; 2001:500:2::c; 2001:500:2d::d; 2001:500:2f::f; 2001:500:9f::42; 2001:500:a8::e; 2001:503:ba3e::2:30; 2001:7fd::1; 2001:7fe::53; 2001:dc3::35; 202.12.27.33".
The IP address lists are strictly formatted and can be captured by a regular expression, and then replaced by a clickable label, e.g.
The zone has NSEC records. Fetched from the nameservers with IP addresses
name server IP list.
The label should also be translatable to work in the context, e.g.
Zonen har NSEC-poster. Hämtad från namnservrarna med IP-adresserna
namnserver-IP-lista.
Clicking on name server IP list should then result in the expanded list:
192.112.36.4; 192.203.230.10; 192.33.4.12; 192.36.148.17; 192.5.5.241; 193.0.14.129; 198.41.0.4; 198.97.190.53; 199.7.83.42; 199.7.91.13; 199.9.14.201; 2001:500:12::d0d; 2001:500:1::53; 2001:500:200::b; 2001:500:2::c; 2001:500:2d::d; 2001:500:2f::f; 2001:500:9f::42; 2001:500:a8::e; 2001:503:ba3e::2:30; 2001:7fd::1; 2001:7fe::53; 2001:dc3::35; 202.12.27.33
Or maybe a sorted list (first IPv4, then IPv6):
192.112.36.4
192.203.230.10
192.33.4.12
192.36.148.17
192.5.5.241
193.0.14.129
198.41.0.4
198.97.190.53
199.7.83.42
199.7.91.13
199.9.14.201
202.12.27.33
2001:500:12::d0d
2001:500:1::53
2001:500:200::b
2001:500:2::c
2001:500:2d::d
2001:500:2f::f
2001:500:9f::42
2001:500:a8::e
2001:503:ba3e::2:30
2001:7fd::1
2001:7fe::53
2001:dc3::35