• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

SIP2SIP: NAPTR record is not valid. NAPTR Record does not validate.

Started by renne, March 09, 2014, 06:32:15 AM

Previous topic - Next topic


I'm trying to add the NAPTR-RRs demanded by SIP2SIP to my zone hosted on the FreeDNS servers.
10  100 "s" "SIPS+D2T" "_sips._tcp.example.com".

But I always get the error messageNAPTR record is not valid. NAPTR Record does not validate.

Is my record wrong or is it incorrectly validated by the FreeDNS form?

Thanx for any hint!  :)


Your record is wrong.  Note the QUOTES and fields.  You probably want this (or something like it):

$ORIGIN example.com      ;Assumed.

@     IN     NAPTR     10     100     "S"     "SIPS+D2T"     ""    _sips._tcp
@     IN     NAPTR     10     100     "S"     "SIP+D2T"       ""    _sip._tcp
@     IN     NAPTR     20     100     "S"     "SIP+D2U"       ""    _sip._udp

_sips._tcp IN SRV     10     100     5061   pbx    ;Or whatever your hostname is for your virtual PBX or phone connection.
_sip._tcp  IN SRV     10     100     5060   pbx
_sip._udp IN SRV     10     100     5060   pbx

pbx     IN     A         ...
pbx     IN     AAAA   ...

You may also need records like:

e164.pbx   IN     NAPTR     10     100     "U"     "E2U+SIP"     "!^\\+([0-9]+)$!sips:\\1@example.com!" .  ;Rewrites to "protocol:_phone#_@example.com"
e164.pbx   IN     NAPTR     20     100     "U"     "E2U+SIP"     "!^\\+([0-9]+)$!sip:\\1@example.com!"  .  ;Fallback to no encryption

The latter will rewrite the telephone number lookup into a URL local for your system.  Then it will use the former type to find and follow the appropriate SRV record.

If you have a real phone number under the "e164.arpa" domain (or alternative), its entry should probably be a CNAME-RR (or if multiple records with the same prefix, a DNAME-RR) pointing to the "e164.pbx.example.com." record(s) created above instead of directly listing the NAPTR records there ("e164.arpa").  Such allows for you to have LOCAL CONTROL over the records to add, change, or delete protocols as needed, and provides for a common interface should you have more than one one number from differing regions or countries.

Although I chose to answer, this really isn't a tunnelbroker DNS question.