| Summary: | ASTERISK-25570: DNS: Implement negative connection cache | ||
| Reporter: | Ashley Sanders (asanders) | Labels: | |
| Date Opened: | 2015-11-18 15:21:22.000-0600 | Date Closed: | 2015-12-02 13:46:38.000-0600 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/DNS |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) ASTERISK-25570-13.diff ( 1) ASTERISK-25570-master.diff ( 2) ASTERISK-25570-test.diff | |
| Description: | What is this? If Asterisk is told to look up a domain, and that domain does not resolve, then Asterisk will temporarily return an error when that domain is looked up. This way, if tons of lookups are attempted, only the first will take time to fail. All subsequent ones will result in an immediate failure since we have cached the failure locally.
| ||
| Comments: | By: Kevin Harwell (kharwell) 2015-12-02 13:44:47.245-0600 After receiving some feedback about implementing a negative DNS cache in Asterisk it was decided that these changes are currently not needed. Instead it makes more sense to use a third party library that does the same thing. However, attaching patches just in case this ever comes up again or needs to be reopened. | ||