Hi,
Okay, *. works perfectly, however, I need to limit the queries to
specific numbers.
As an example
0.0.1.0.9.6.4.1.2.7.2.domain1.com
3.8.6.2.7.4.7.2.8.7.2.domain2.net
8.1.5.1.0.5.3.7.8.7.2.domain3
As per above, the number portion [0-9].[0-9]... will need to be
specific, while the domain port
Hi,
Okay, *. works perfectly, however, I need to limit the queries to
specific numbers.
As an example
0.0.1.0.9.6.4.1.2.7.2.domain1.com
3.8.6.2.7.4.7.2.8.7.2.domain2.net
8.1.5.1.0.5.3.7.8.7.2.domain3
As per above, the number portion [0-9].[0-9]... will need to be
specific, while the domain port
> I did try the following:
>
> 7.7.7.5.2.1.4.4.9.9.8.1.2.*
The "*" wildcard must be the first label.
___
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
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
> 7.7.7.5.2.1.4.4.9.9.8.1.2.INNAPTR10010"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)
Hi Everyone.
I've been trying to get a solution working where by I need to supply a
response based on a NAPTR query. The problem is, the domain section of
the NAPTR needs to be "dynamic", as this could be different per query. I
based my config on the following url, and all works well for A record
6 matches
Mail list logo
