Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem configuring NAPTR with BIND

558 views
Skip to first unread message

Sachin Kamat

unread,
Oct 26, 2006, 11:34:40 AM10/26/06
to

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 "e164.arpa" {

type master;
notify no;

allow-query { any; };
file "enum.zone";

};

************************
And enum.zone looks like

$TTL 300
@ IN SOA ns1.e164.arpa. hostmaster.e164.arpa. (
200211152 ; serial#
3600 ; refresh, seconds
3600 ; retry, seconds
3600 ; expire, seconds
3600 ) ; minimum, seconds

NS www ; Inet Address of nameserver
ns1 A 50.50.50.27
localhost A 127.0.0.1
$ORIGIN 4.3.0.6.9.4.6.1.1.4.4.e164.arpa.
8 IN NAPTR 10 100 "u" "e2u+sip" "!^.*$!sip:in...@sachin.com!" .
5.4 IN NAPTR 10 100 "u" "E2U+service:SIP" "!^.*$!sip:in...@sachin.com!"
.
4.8 IN NAPTR 10 100 "u" "E2U+service:SIP" "!^.*$!sip:in...@sachin.com!"
.


***************


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

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"

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.

Thanks,
Sachin


Jim Reid

unread,
Oct 26, 2006, 12:24:37 PM10/26/06
to
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.


0 new messages