Wildcard depth on NAPTR records

Ejay Hire ejay.hire at isdn.net
Thu Feb 2 22:05:04 UTC 2006


Hello all.

I have a unusual problem.  We use DNS for telephone routing.
I have a dns zone that contains NAPTR records, and have run
in to the following problem.

If I query my ns4, I get the proper response.  If I query my
other server, I get a NXDOMAIN response.  NS4 is the master,
the other server is a slave.  Replication is working
properly, and both servers answer properly for other
queries, in the same zone file.

I'm querying for 5.5.5.5.5.5.5.5.6.8.1.e164-pstn.isdn.net

The wildcard entry that should match it in the zone file is

*.1               IN NAPTR 100 11 "u" "E2U+SIP"
"!^\\+*(.*)$!sip:\\1 at telco01.isdn.net!".     

But when I do the following I get different results...  (on
ns4)
host -t NAPTR 5.5.5.5.5.5.5.5.6.8.1.e164-pstn.isdn.net 
5.5.5.5.5.5.5.5.6.8.1.e164-pstn.isdn.net NAPTR 100 11 "u"
"E2U+SIP" "!^\\+*(.*)$!sip:\\1 at telco01.isdn.net!" .

host -t NAPTR 5.5.5.5.5.5.5.5.6.8.1.e164-pstn.isdn.net
telco07.isdn.net
Using domain server:
Name: telco07.isdn.net
Address: 207.65.69.254#53
Aliases: 

Host 5.5.5.5.5.5.5.5.6.8.1.e164-pstn.isdn.net not found:
3(NXDOMAIN)


I'm running the following versions.
[ejay.hire at ns4 ejay.hire]$ rpm -qa bind
bind-9.2.2.P3-9
[root at telco07 ~]# rpm -qa bind
bind-9.3.1-14_FC4

Anyone see a cause for this?

Thanks,
Ejay 



More information about the bind-users mailing list