Starsky, I had expected that DNS requests for 2.5.7.0.5.5.5.0.5.6.e164.arpa would receive an NXDOMAIN response, but it looks like this doesn't happen. In fact, this seems to be a recent DNS change to 5.6.e164.arpa because some of our servers are exhibiting the same behavior. Requests for many other e164.arpa domains do return NXDOMAIN as expected.
I think the best solution here is either to set your DNS server to return NXDOMAIN for "e164.arpa" or to use the temporary workaround I mentioned previously. However, I'm going to investigate further on this - I suspect we should be disabling ENUM by default. You asked about DNS servers, we use either/both of BIND and dnsmasq for our DNS solutions. On BIND, we configure an e164.arpa zone as follows: $TTL 1h @ IN SOA e164.arpa [email protected] ( 2009010910 ;serial 3600 ;refresh 3600 ;retry 3600 ;expire 3600 ;minimum TTL ) @ IN NS e164.arpa. @ IN A <DNS server's IP address> ; Route all numbers to local domain * IN NAPTR 1 1 "u" "E2U+sip" "!(^.*$)!sip:\\1@<deployment home domain>!" . I hope that helps. Please let me know how you get on. Thanks, Matt From: Starsky Wong [mailto:[email protected]] Sent: 11 August 2013 15:41 To: Matt Williams Cc: clearwater Subject: Re: [Clearwater] Two online client cannot communicate to each other HI Matt, Thanks for you email. Our DNS server will forward dns request if it cannot resolve (i.e., our nodes can resolve DNS request like google.com<http://google.com>, ubuntu.com<http://ubuntu.com>, etc) . Does sprout expect to get NXDOMAIN on this ? If it does, my guess is the DNS should set to return NXDOMAIN for zone "e164.arpa", am I correct ? May I ask how if you can share with us what is the DNS Server setting in your testbed ? Thanks again :) Starsky H.Y. Wong
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
