Hi out there
The last few days I noticed quite a large delay when I first dial a number from my asterisk server.
I found that the problem is that the 1.4.e164.arpa lookup takes enormous time to return a NXDOMAIN
== ast_get_enum(num='+41618269309', tech='sip', suffix='e164.arpa', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.arpa, 5148 ms
compared to the e164.org or e164.info lookups:
== ast_get_enum(num='+41618269309', tech='sip', suffix='e164.org', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.org, 141 ms
== ast_get_enum(num='+41618269309', tech='sip', suffix='e164.info', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.info, 167 ms
Of course, as soon as the NXDOMAIN is in the local DNS cache, dialing the same number is fast again.
Also the previously working ETHZ e164.arpa test-tone number cannot be resolved anymore:
== ast_get_enum(num='+41446580004', tech='sip', suffix='e164.arpa', options='', record=1 == ast_get_enum() profiling: FAIL, 4.0.0.0.8.5.6.4.4.1.4.e164.arpa, 5150 ms
Has switch ceased to offer e164.arpa entries? 1.4.e164.arpa does not seem to be delegated anymore:
; <<>> DiG 9.6-ESV-R1 <<>> NS 1.4.e164.arpa. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49396 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION: ;1.4.e164.arpa. IN NS
;; AUTHORITY SECTION: e164.arpa. 10784 IN SOA ns-pri.ripe.net. e164-contacts.ripe.net. 2010062458 14400 3600 2419200 14400
Deleagions found by dnsbajaj: Subdomains: 0.1.8.7.8.e164.arpa , 0.2.4.e164.arpa , 0.3.e164.arpa , 0.4.e164.arpa , 0.6.e164.arpa , 0.7.3.e164.arpa , 0.8.3.e164.arpa , 0.9.2.e164.arpa , 0.9.5.e164.arpa , 1.2.4.e164.arpa , 1.3.e164.arpa , 1.6.e164.arpa , 1.7.9.e164.arpa , 1.8.e164.arpa , 2.6.2.e164.arpa , 2.6.9.e164.arpa , 2.6.e164.arpa , 2.8.e164.arpa , 3.2.4.e164.arpa , 3.3.e164.arpa , 3.4.e164.arpa , 3.5.3.e164.arpa , 3.6.e164.arpa , 4.3.2.8.8.e164.arpa , 4.4.e164.arpa , 4.5.3.e164.arpa , 4.7.3.e164.arpa , 4.8.e164.arpa , 4.9.5.e164.arpa , 5.5.2.e164.arpa , 5.5.e164.arpa , 5.6.e164.arpa , 6.3.e164.arpa , 6.4.2.e164.arpa , 6.4.e164.arpa , 6.6.e164.arpa , 6.8.3.e164.arpa , 6.8.8.e164.arpa , 6.8.e164.arpa , 6.9.5.e164.arpa , 7.4.2.e164.arpa , 7.4.e164.arpa , 8.0.5.e164.arpa , 8.4.e164.arpa , 8.5.3.e164.arpa , 9.3.e164.arpa , 9.4.e164.arpa , 9.5.3.e164.arpa
-Benoît-
On Thu, 24 Jun 2010 15:33:28 +0200, Benoit Panizzon panizzon@woody.ch said:
Hi out there The last few days I noticed quite a large delay when I first dial a number from my asterisk server.
I found that the problem is that the 1.4.e164.arpa lookup takes enormous time to return a NXDOMAIN
== ast_get_enum(num='+41618269309', tech='sip', suffix='e164.arpa', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.arpa, 5148 ms
That looks like a timeout of 5 seconds. Maybe your cache is unable to reach some of the e164.arpa servers?
compared to the e164.org or e164.info lookups:
== ast_get_enum(num='+41618269309', tech='sip', suffix='e164.org', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.org, 141 ms
== ast_get_enum(num='+41618269309', tech='sip', suffix='e164.info', options='', record=1 == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.info, 167 ms
Of course, as soon as the NXDOMAIN is in the local DNS cache, dialing the same number is fast again.
Also the previously working ETHZ e164.arpa test-tone number cannot be resolved anymore:
== ast_get_enum(num='+41446580004', tech='sip', suffix='e164.arpa', options='', record=1 == ast_get_enum() profiling: FAIL, 4.0.0.0.8.5.6.4.4.1.4.e164.arpa, 5150 ms
Has switch ceased to offer e164.arpa entries? 1.4.e164.arpa does not seem to be delegated anymore:
This "enum pilot" was terminated many, many moons ago. The zone was still delegated to us until November last year, but it has been empty for several years.
-
Alexander Gall -
Benoit Panizzon