Hi, I did try the following:
7.7.7.5.2.1.4.4.9.9.8.1.2.* Which sadly did not work. Below is an example of queries that I would typically need to process. In all examples, the number will be the same, its just the domain portion that will change based on the environment: 7.7.7.5.2.1.4.4.9.9.8.1.2.domain1.com 7.7.7.5.2.1.4.4.9.9.8.1.2.domain2.com 7.7.7.5.2.1.4.4.9.9.8.1.2.domain3 (intentionally left this one without a .tld) 7.7.7.5.2.1.4.4.9.9.8.1.2.domain4 7.7.7.5.2.1.4.4.9.9.8.1.2.domain5 7.7.7.5.2.1.4.4.9.9.8.1.2.127.0.0.1 7.7.7.5.2.1.4.4.9.9.8.1.2.196.43.1.1 While the above is only a few examples and seems to be fairly simple to put together, the domains will change dramatically, which makes it quite an administrative task to keep building authoritative zones for each domain - thats why I was hoping it might be possible to achieve this via a wildcard. Many thanks Doug On 2012/01/09 9:43 PM, Florian Weimer wrote: >> 7.7.7.5.2.1.4.4.9.9.8.1.2. IN NAPTR 100 10 "u" "E2U+sip" >> "!(^.*$)!sip:2799820784000132" . ; Testing > This isn't a wildcard, so it will not match as a wildcard. > > Can you provide a few example RRs which you want to synthesize using > wildcards? It's not clear (to me at least) what you're trying to do. > There is a good chance that you have to change the regexp part of the > NAPTR record. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
