| Summary: | ASTERISK-18351: dnsmgr sets port to 0 after a failed DNS lookup | ||
| Reporter: | Mike (panic) | Labels: | |
| Date Opened: | 2011-08-26 14:52:53 | Date Closed: | 2011-09-15 10:22:35 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/Netsock |
| Versions: | 1.8.4 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Asterisk 1.8.4.2 on CentOS 5.5 x86_64 | Attachments: | |
| Description: | After a system reboot, Asterisk started up properly, but it's possible the network wasn't up yet, so the initial DNS lookup on a SIP host name failed. A few minutes later, once the network was up, it made a successful DNS lookup, but the SIP port was set to 0. In my sip.conf file, I did not have a port specified; none of my SIP peers have a port specified, but they all defaulted to 5060 as I would expect. Adding a port number to the SIP peers fixes the issue, but I would expect that after a DNS lookup failure, the port number would not be reset, or it would be set back to the default value of 5060. (we aren't using DNS SRV records) and only in cases where you wanted to use a non-standard port, would you have to specify the port option. [Aug 20 17:28:26] NOTICE[2961] dnsmgr.c: dnssrv: host 'sip.faktortel.com.au' changed from 202.43.66.5:5060 to 202.43.66.3:5060 [Aug 20 18:21:07] ERROR[2946] netsock2.c: getaddrinfo("sip.faktortel.com.au", "(null)", ...): Name or service not known [Aug 20 18:21:07] WARNING[2946] acl.c: Unable to lookup 'sip.faktortel.com.au' [Aug 20 18:35:08] NOTICE[2962] dnsmgr.c: dnssrv: host 'sip.faktortel.com.au' changed from (null) to 202.43.66.1:0 | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-08-30 13:51:23.682-0500 I think you recently fixed this right Terry? Can you close it out if you did? If not assign it back to me. By: Terry Wilson (twilson) 2011-08-30 13:53:42.780-0500 I haven't fixed it to my knowledge, but I did fix a different DNS issue. By: Leif Madsen (lmadsen) 2011-09-01 09:58:25.412-0500 I see this was reported against 1.8.4. Could you please test 1.8.6.0 and see if this is fixed? I've experienced something like this, but haven't had that problem since 1.8.5.0. By: Leif Madsen (lmadsen) 2011-09-15 10:22:30.366-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines By: Mike (panic) 2011-09-15 18:24:13.372-0500 I only received an e-mail response about this today when it was closed. I also don't have access to, nor have I ever used IRC- so I wouldn't know how to contact marshal in #asterisk-bugs to get him to re-open this. In response to Leif Madsen; I don't have a test system to run 1.8.6.0 on to try and see if this has gone away, so unfortunately I can't check to see if it's fixed. I went through the 1.8.60 changelog and I didn't see anything that looked related. Mike | ||