wildcard NAPTR problems, bind8 and bind9
John Brown
john+bind at chagres.net
Tue Mar 30 04:18:26 UTC 2004
Hi List,
another NAPTR problem....
*.8.enum.example.net. 15 IN NAPTR 100 10 "u" "E2U+IAX2" "!\\^*$!iax2:vgw-01.abq.us.example.com/\\1!" .
in a BIND 8.4.4 or a BIND 9.2.3 server
gives
endor# dig 2.1.1.1.1.2.8.enum.example.net naptr
; <<>> DiG 8.4 <<>> 2.1.1.1.1.2.8.enum.example.net naptr
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31782
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;; 2.1.1.1.1.2.8.enum.example.net, type = NAPTR, class = IN
;; AUTHORITY SECTION:
example.net. 30S IN SOA ns1.example.net. hostmaster.example.net. (
2004032923 ; serial
30S ; refresh
15S ; retry
1W ; expiry
30S ) ; minimum
;; Total query time: 1 msec
;; FROM: endor.example.net to SERVER: 127.0.0.1
;; WHEN: Mon Mar 29 21:15:36 2004
;; MSG SIZE sent: 49 rcvd: 115
shouldn't a wildcard mean match anthing that has at least 8.enum.example.net. ????
or is weeks of little to no sleep causing me to make a dummy mistake ??
john brown
chagres technologies, inc (americas)
chagres technologies, b.v. (emea)
chagres technologies, pty ltd. (australia / asia)
albuquerque -- rotterdam -- sydney
More information about the bind-users
mailing list