<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hallo Mihi!<br>
<br>
Siehe: <a class="moz-txt-link-freetext" href="http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html">http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html</a><br>
................................................................................................................<br>
<h2>NAME</h2>
dnsmasq - A lightweight DHCP and caching DNS server.
<a name="lbAC"> </a>
<h2>SYNOPSIS</h2>
<b>dnsmasq</b>
<i>[OPTION]...</i>
<a name="lbAD"> </a>
<h2>DESCRIPTION</h2>
<b>dnsmasq</b>
is a lightweight DNS, TFTP and DHCP server. It is intended to
provide coupled DNS and DHCP service to a LAN.
<p>
Dnsmasq accepts DNS queries and either answers them from a small,
local,
cache or forwards them to a real, recursive, DNS server. It loads
the
contents of /etc/hosts so that local hostnames
which do not appear in the global DNS can be resolved and also
answers
DNS queries for DHCP configured hosts.
</p>
<p>
The dnsmasq DHCP server supports static address assignments and
multiple
networks. It automatically
sends a sensible default set of DHCP options, and can be
configured to
send any desired set of DHCP options, including
vendor-encapsulated
options. It includes a secure, read-only,
TFTP server to allow net/PXE boot of DHCP hosts and also supports
BOOTP.
</p>
<p>
Dnsmasq supports IPv6 for all functions and a minimal
router-advertisement daemon.
<a name="lbAE"> </a>
</p>
................................................................................................................<br>
<br>
<br>
Am 2012-06-14 10:29, schrieb Michael Bauer:
<blockquote cite="mid:20120614082940.GS1450@lenore.fritz.box"
type="cite">
<pre wrap="">DNSMasq is just a DNS forwarder "Dnsmasq is targeted at home networks using
NAT"</pre>
</blockquote>
Das muss eine ältere Beschreibung sein.<br>
<blockquote cite="mid:20120614082940.GS1450@lenore.fritz.box"
type="cite">
<pre wrap="">
Sind wir doch nicht? Ich nehm an, der ist wegen seinen dhcp faehigkeiten da</pre>
</blockquote>
Zum Teil schon. Außerdem ist er in den OpenWRT-Images genauso
drinnen.<br>
<blockquote cite="mid:20120614082940.GS1450@lenore.fritz.box"
type="cite">
<pre wrap="">
noch drauf (oder einfach weil das mal home router waren). Koennen wir nicht
eh ganz auf den verzichten?</pre>
</blockquote>
Warum sollten wir? Richtig konfiguriert hat er mehr Vorteile als
Nachteile.<br>
<br>
<blockquote cite="mid:20120614082940.GS1450@lenore.fritz.box"
type="cite">
<pre wrap="">
Mihi</pre>
</blockquote>
SG<br>
Erich<br>
<blockquote cite="mid:20120614082940.GS1450@lenore.fritz.box"
type="cite">
<pre wrap="">
On Wed, Jun 13, 2012 at 02:22:05PM +0200, Markus Gschwendt wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, 2012-06-13 at 11:22 +0200, Michael Bauer wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hint: Einfach den DNS server eintragen, der vom DNSmasq gefragt wird, sollt
gehn. Und ja man kann dem DHCP server normalerweise sagen welchen DNS
Server man fragen will (wieso da ueberhaupt ein dnsmasq drauf ist, ist mir
raetselhaft).
</pre>
</blockquote>
<pre wrap="">
der dnsmasq _ist_ der dhcp server.
markus
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>