[asterisk-bugs] [JIRA] (ASTERISK-28004) PjSIP dns breaks when using ::1 in /etc/resolv.conf

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244573#comment-244573 ] 

Richard Mudgett commented on ASTERISK-28004:
--------------------------------------------

Not to mention that bundled has patches applied and is configured to work in server mode.

> PjSIP dns breaks when using ::1 in /etc/resolv.conf
> ---------------------------------------------------
>
>                 Key: ASTERISK-28004
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28004
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.22.0
>         Environment: CentOS 7.4 64bit
>            Reporter: Isaac McDonald
>            Assignee: Isaac McDonald
>              Labels: pjsip
>
> PJSIP DNS resolution breaks when using the IPv6 loopback address as a nameserver in /etc/resolve.conf.
> Steps to reproduce: Note that the hostname used in the AOR had a TTL of 60 seconds during my testing to force pjsip not to cache the results
> 1. Install dnsmasq "yum install dnsmasq"
> 2. create /etc/dnsmasq.d/dns.conf and add the following:
> listen-address=::1,127.0.0.1
> no-resolv
> server=1.1.1.1
> 3. Set nameserver in /etc/resolv.conf to IPv6 localhost address:
> nameserver ::1
> 4. Create a pjsip trunk to register with a hostname in the aor. example:
> contact=sip:someuser at testhost.example.com:5060
> 5. Note how SIP registrations to the sip trunk fail. Note how calls via the trunk also fail. It may take a few minutes before you get failures. 
> 6. Note the following messages in the asterisk log:
> 'No working DNS nameserver (PJLIB_UTIL_EDNSNOWORKINGNS)' sending OPTIONS request to endpoint
> 7. Change the nameserver in /etc/resove.conf to:
> nameserver 127.0.0.1
> 8. Reload asterisk "asterisk -rx"core reload"
> 9. Note how the trunk created in step 4 registers. Calls placed via the trunk also complete.



--
This message was sent by Atlassian JIRA
(v6.2#6252)