[Pdns-users] Wildcard NAPTRs
bcrawfo2
scott-forum at scottkate.com
Sun Apr 26 10:58:23 UTC 2009
I'm trying to set up PowerDNS to be an enum server that can answer wildcards.
So...I want to be able to respond to entire blocks of numbers with a single
database entry.
I swear I had this working just the other day on a test system (which I
stupidly cleaned up).
Here is my DB
select * from records where type='NAPTR';
+----+-----------+---------------------+-------+--------------------------------------------------------+------+------+-------------+
| id | domain_id | name | type | content
| ttl | prio | change_date |
+----+-----------+---------------------+-------+--------------------------------------------------------+------+------+-------------+
| 16 | 1 | *.0.0.1.e164.pdns | NAPTR | 100 10 "u" "E2U+sip"
"!^.*$!sip:hello at mydomain.net!" . | 600 | NULL | NULL |
| 17 | 1 | 4.4.4.4.4.e164.pdns | NAPTR | 100 10 "u" "E2U+sip"
"!^.*$!sip:hello at mydomain.net!" . | 600 | NULL | NULL |
+----+-----------+---------------------+-------+--------------------------------------------------------+------+------+-------------+
I can make basic queries shown here.
nslookup -q=naptr 4.4.4.4.4.e164.pdns 127.0.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53
4.4.4.4.4.e164.pdns naptr = 100 10 "u" "E2U+sip"
"!^.*$!sip:hello at mydomain.net!" .
But when I try to use the first record...no go.
nslookup -q=naptr 1.0.0.1.e164.pdns 127.0.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
*** Can't find 1.0.0.1.e164.pdns: No answer
Authoritative answers can be found from:
e164.pdns nameserver = test37.something.something.com.
test37.something.something.com internet address = someip.someip.233.173
Thanks for any input.
--
View this message in context: http://www.nabble.com/Wildcard-NAPTRs-tp23241127p23241127.html
Sent from the PowerDNS mailing list archive at Nabble.com.
More information about the Pdns-users
mailing list