DNS Snooping
Charging
The charging of DNS Snooping takes place at SM-P.
Rule Definitions
ruledef <ruledef_name>
ip [server-domain-name {contains|=|ends-with|starts-with} <url_string> ]
ip [server-domain-name {contains|=|ends-with|starts-with} <url_string> ]
multi-line-OR enabled
ruledef <ruledef_name>
no ip [server-domain-name {contains|=|ends-with|starts-with} <url_string> ]
exit
configure
active-charging service service_name
ip dns-resolved-entries timeout <value_secs>
end
Whenever the ruledef containing the ip server-domain-name keyword is defined and used in rulebase, the ip-table is created per rulebase per instance.Rule Matching
The functionality remains the same as the non-CUPS architecture.
Show CLIs
Use the following CLIs to check the table for DNS IP entries:show user-plane-service [ statistics dns-learnt-ip-addresses {summary | sessmgr instance <id> |all [ verbose ] } ]
Bulkstats
The following bulkstats are available in support of DNS Snooping feature:
-
ecs-dns-learnt-ipv4-entries
-
ecs-dns-flushed-ipv4-entries
-
ecs-dns-replaced-ipv4-entries
-
ecs-dns-overflown-ipv4-entries
-
ecs-dns-learnt-ipv6-entries
-
ecs-dns-flushed-ipv6-entries
-
ecs-dns-replaced-ipv6-entries
-
ecs-dns-overflown-ipv6-entries
The above bulkstats are added in the ECS schema same as in the non-CUPS architecture.
Note | The SNMP Trap generation commands are not supported in CUPS DNS snooping feature. |