<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/dproxy/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/dproxy/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 06 Jun 2004 22:48:01 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/dproxy/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>EDNS Support (RFC2671)</title><link>https://sourceforge.net/p/dproxy/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Just switched to ADSL with a Netgear DG834. It uses dproxy-nexgen (patched).&lt;/p&gt;
&lt;p&gt;My local (home) DNS is bind9 and it took a while with tcpdump to work out why I couldn't forward the root zone through dproxy on the DG834: bind9 uses RFC2671 Extended DNS protocol by default. Problem "solved" by adding a 'server 192.168.0.1 {edns no;};' statement to named.conf, but it would be nice not to have to go through that pain.&lt;/p&gt;
&lt;p&gt;I'm not sure how much work it would take to support RFC2671. Possibly just add a note in the README about bind9 interraction insted?&lt;/p&gt;
&lt;p&gt;Dave G.&lt;br /&gt;
daveg at dgnode dot sceaming dot net&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 06 Jun 2004 22:48:01 -0000</pubDate><guid isPermaLink="false">https://sourceforge.nete182c2ccc6a21a0d5c2d57ea7644ee116dcefef1</guid></item><item><title>dproxy-nextgen for multiple connections</title><link>https://sourceforge.net/p/dproxy/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;With dproxy-nextgen the nameserver to be used is&lt;br /&gt;
defined in the configuration file.&lt;br /&gt;
i am using multiple dial-up connections with&lt;br /&gt;
different nameservers, which are assigned via ppp.&lt;br /&gt;
i am now wondering if it would be a better solution&lt;br /&gt;
to have dproxy check the resolv.conf file and&lt;br /&gt;
use the nameserver found there (and check for changes &lt;br /&gt;
in resolv.conf before dproxy contacts the nameserver)&lt;br /&gt;
instead of having to define another one in dproxy.conf &lt;br /&gt;
?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 12 Mar 2001 09:44:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1882dc96273c4aa60b53214ee1a933047053ae7e</guid></item></channel></rss>