https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-02-11T10:50:31ZpfSense bugtrackerpfSense - Bug #5882: XMLRPC sync tests for DNS Forwarder and Resolver are incorrect, will disable one in a valid configurationhttps://redmine.pfsense.org/issues/5882?journal_id=251702016-02-11T10:50:31ZJim Pingle
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/25170/diff?detail_id=19132">diff</a>)</li></ul> pfSense - Bug #5882: XMLRPC sync tests for DNS Forwarder and Resolver are incorrect, will disable one in a valid configurationhttps://redmine.pfsense.org/issues/5882?journal_id=251822016-02-12T06:58:50ZJim Pingle
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/25182/diff?detail_id=19144">diff</a>)</li></ul> pfSense - Bug #5882: XMLRPC sync tests for DNS Forwarder and Resolver are incorrect, will disable one in a valid configurationhttps://redmine.pfsense.org/issues/5882?journal_id=251842016-02-12T12:20:12ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Refine the way the DNS Forwarder and DNS Resolver are handled via XMLRPC. Fixes #5882" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/57b5da701888602edb008fbd55f6e55e18578eb8">57b5da701888602edb008fbd55f6e55e18578eb8</a>.</p> pfSense - Bug #5882: XMLRPC sync tests for DNS Forwarder and Resolver are incorrect, will disable one in a valid configurationhttps://redmine.pfsense.org/issues/5882?journal_id=252112016-02-14T21:19:38ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul> pfSense - Bug #5882: XMLRPC sync tests for DNS Forwarder and Resolver are incorrect, will disable one in a valid configurationhttps://redmine.pfsense.org/issues/5882?journal_id=252132016-02-15T08:40:00ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Updated and tested this again each way (one enabled, the other enabled, both enabled, etc) and each time the behavior was correct after my last change. The services are started and stopped as expected now.</p>