Problem configuring NAPTR with BIND
jim at rfc1035.com
Thu Oct 26 16:24:37 UTC 2006
On Oct 26, 2006, at 16:34, Sachin Kamat wrote:
> I am querying for number +44 1164960348 (i.e.
> It says "NAPTR record unmatched"
There's no delegation for 22.214.171.124.126.96.36.199.188.8.131.52.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
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://
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 184.108.40.206.220.127.116.11.18.104.22.168.e164.arpa. The second one is for
22.214.171.124.126.96.36.199.188.8.131.52.4.4.e164.arpa. And the third is for
184.108.40.206.220.127.116.11.18.104.22.168.22.214.171.124.e164.arpa. That's probably not what
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.
More information about the bind-users