Problem configuring NAPTR with BIND

Sachin Kamat Sachin.Kamat at
Thu Oct 26 15:34:40 UTC 2006

Hi ,

I have really spent a whole day doing this still unsuccessful. 

Can anybody please throw any light on this ??

I have installed bind-9.2.4-2

Then I tried configuring NAPTR

My named.conf looks like

// Default named.conf generated by install of bind-9.2.4-2
options {
        directory "/var/named";
        dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
include "/etc/rndc.key";

zone "" {

   type master;
   notify no;

   allow-query { any; };
   file "";


And looks like

$TTL 300
@       IN      SOA (
                       200211152       ; serial#
                       3600            ; refresh, seconds
                       3600            ; retry, seconds
                       3600            ; expire, seconds
                       3600 )          ; minimum, seconds

                NS      www             ; Inet Address of nameserver
ns1           A
localhost     A
8  IN  NAPTR 10 100 "u" "e2u+sip" "!^.*$!sip:info at!" .
5.4  IN  NAPTR 10 100 "u" "E2U+service:SIP" "!^.*$!sip:info at!"
4.8  IN  NAPTR 10 100 "u" "E2U+service:SIP" "!^.*$!sip:info at!"


I am using enum client provided by JPRS (Japan registration etc.)

I am querying for number +44 1164960348 (i.e.

It says "NAPTR record unmatched"

If I give a totally vague number  (like +44 1164960349)then it says "DNS
name does not exist"

Which means it is able to locate the number but somehow not able to
retrieve the NAPTR. 

Can anybody please let me know what is going wrong here ?? 
Where is it trying to match the NAPTR record??

That will help a lot.


More information about the bind-users mailing list