1The "wildcard" DLZ module provides a "template" zone for domains matching 2a wildcard name. For example, the following DLZ configuration would match 3any zone name containing the string "example" and ending with .com, such 4as "thisexample.com", "exampleofthat.com", or "anexampleoftheotherthing.com". 5 6 dlz "test" { 7 database "dlopen ../dlz_wildcard_dynamic.so 8 *example*.com 10.53.* 1800 9 @ 3600 SOA {ns3.example.nil. support.example.nil. 42 14400 7200 2592000 600} 10 @ 3600 NS ns3.example.nil. 11 @ 3600 NS ns4.example.nil. 12 @ 3600 NS ns8.example.nil. 13 @ 3600 MX {5 mail.example.nil.} 14 ftp 86400 A 192.0.0.1 15 sql 86400 A 192.0.0.2 16 tmp {} A 192.0.0.3 17 www 86400 A 192.0.0.3 18 www 86400 AAAA ::1 19 txt 300 TXT {\"you requested $record$ in $zone$\"} 20 * 86400 A 192.0.0.100"; 21 }; 22 23For any zone name matchin the wildcard, it would return the data from 24the template. "$zone$" is replaced with zone name: i.e., the shortest 25possible string of labels in the query name that matches the wildcard. 26"$record$" is replaced with the remainder of the query name. In the 27example above, a query for "txt.thisexample.com/TXT" would return the 28string "you requested txt in thisexample.com". 29 30Any client whose source address matches the second wildcard ("10.53.*") 31is allowed to request a zone transfer. 32