Summary: | DNS Cache Manager - custom DNS resolver doesn't use system resolver by default | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Konstantin Kalinin <konstantin> |
Component: | HTTP | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | minor | Keywords: | FixedInTrunk |
Priority: | P2 | ||
Version: | 5.2.1 | ||
Target Milestone: | JMETER_5.3.0 | ||
Hardware: | PC | ||
OS: | All | ||
Attachments: | Example configuration |
Description
Konstantin Kalinin
2020-04-07 07:45:07 UTC
I think you are right and it should fallback to the system DNS resolver. Patches are welcome (sorry for the late reply) @Konstantin, could you test the next build from trunk or nightly? commit da5fb8319b02666062e415f4823ee4bcde2a8639 Author: Felix Schumacher <felix.schumacher@internetallee.de> AuthorDate: Sat Jan 2 21:26:44 2021 +0100 DNS Cache Manager - custom DNS resolver does not use system resolver by default Bugzilla Id: 64318 --- .../apache/jmeter/protocol/http/control/DNSCacheManager.java | 7 +++---- .../jmeter/protocol/http/control/DNSCacheManagerSpec.groovy | 10 ++++++++++ xdocs/changes.xml | 1 + 3 files changed, 14 insertions(+), 4 deletions(-) Closed, as no feedback probably means, it works. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5287 |