<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<br>
On 08/12/2009 11:07 AM, Helmut Hullen wrote:
<blockquote cite="mid:B6jird$USsB@helmut.hullen.de" type="cite">
<pre wrap="">Hallo, JD,
<a class="moz-txt-link-abbreviated" href="mailto:jd1008@gmail.com">jd1008@gmail.com</a> meinte am 12.08.09 in dnsmasq zum Thema Re: [Dnsmasq-discuss] router won't query itsself:
</pre>
<blockquote type="cite">
<pre wrap="">/etc/resolv.conf must ONLY contain
nameserver 127.0.0.1
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">AND
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">/etc/dnsmasq.conf must set
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">resolv-file=/etc/resolv.dnsmasq
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">Or whatever you decide to call that file, which contains the list of
the real nameservers.
</pre>
</blockquote>
<pre wrap=""><!---->
Just a (not tested) idea:
pppoe and router connections into the WAN lead (in many distributions)
to a file "/etc/ppp/resolv.conf" which contains the 2 nameservers the
ISP proposes.
"resolv-file" may lead to this file.
Viele Gruesse!
Helmut
__</pre>
</blockquote>
Hi Helmut,<br>
Even so, I do not see the need to let the host be bothered by a
changing IP address provided by the ISP.<br>
Let all that be handled by a cheap router, whose LAN ip address remains
constant to the lan in it's<br>
subnet for which it is the gateway. You can always query the router for
what IT'S nameservers (provided<br>
by the ISP) are.<br>
<br>
I am surprised that people are making work for themselves for nothing.<br>
<br>
Cheers,<br>
<br>
JD<br>
</body>
</html>