Problem configuring NAPTR with BIND

[Jim Reid]

On Oct 26, 2006, at 16:34, Sachin Kamat wrote:

> I am querying for number +44 1164960348 (i.e.
> 8.4.3.0.6.9.4.6.1.1.4.4.e164.arpa)
>
> It says "NAPTR record unmatched"

There's no delegation for 8.4.3.0.6.9.4.6.1.1.4.4.e164.arpa. It  
doesn't live on the public internet. Fix that. Then fix your zone  
file. It has only one NS record. And that points at a non-existent  
hostname.

The RDATA for the NAPTR records in your zone file is wrong. Their  
services fields are broken. "e2u+sip" is OK (ish). "E2U+voice:sip"  
would be better. "E2U+service" is illegal. The list of valid strings  
that can be used in place of "service" -- ie the names of the  
services available for some NAPTR record -- can be found at: ftp:// 
ftp.iana.org/assignments/enum-services.

The owner-names of your NAPTRs look to be broken too. This wouldn't  
be the case if you used fully qualified and dot-terminated names  
EVERYWHERE. As everyone should. Your zone file's first NAPTR record  
is for 8.4.3.0.6.9.4.6.1.1.4.4.e164.arpa. The second one is for  
5.4.8.4.3.0.6.9.4.6.1.1.4.4.e164.arpa. And the third is for  
4.8.5.4.8.4.3.0.6.9.4.6.1.1.4.4.e164.arpa. That's probably not what  
you wanted.

Oh and the expire, refresh, retry and negative TTL values in your  
zone's SOA record leave a lot to be desired.
They make syntactic sense. But no semantic sense.