<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.network.dns.dnsmasq.general">
    <title>gmane.network.dns.dnsmasq.general</title>
    <link>http://blog.gmane.org/gmane.network.dns.dnsmasq.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5861"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5859"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5851"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5842"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5838"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5834"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5832"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5824"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5818"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5816"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5804"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5795"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5787"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5786"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5784"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5779"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5777"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5775"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5771"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5764"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5861">
    <title>release for debian / ARMv5?</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5861</link>
    <description>&lt;pre&gt;Can anyone tell me, if and where I can get a Debian "testing" version of
IPv6 enabled DnsMasq for Squeeze 2.6.38.8 armv5tel?
I don't like to compile it by myself, so I hope anybody here has contact
to the .deb packet maintainer here , or just knows about the state.

Same question aplies for SlugOS/LE 5.3 (2.6.27.8) from Optware with:
    Dnsmasq version 2.47  Copyright (C) 2000-2009 Simon Kelley
    Compile time options IPv6 GNU-getopt no-DBus no-I18N TFTP

regards,
MM
&lt;/pre&gt;</description>
    <dc:creator>Modem Man</dc:creator>
    <dc:date>2012-05-25T13:00:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5859">
    <title>A (possibly bad) idea: failover in dnsmasq</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5859</link>
    <description>&lt;pre&gt;Starting just a few days before the day the machine running dnsmasq in
my SOHO died, I was giving some thought to how I'd go about ensuring
a backup copy of dnsmasq could take over if my only running instance
died. Needless to say, the death of the machine left my small network in
shambles, because I couldn't connect to anything to fix things without
first configuring temporary static addresses; sans DHCP, stuff fails... :)

I'm anything but a DHCP specialist, but I want to bounce this idea off
you anyway, even if you mind. ;-)

The trick, as I understand it, in setting up more than a single dnsmasq
instance in a network, is to ensure that it uses --dhcp-script to STORE
the leases and --leasefile-ro to force the script to produce a list of
current leases ("init") from which a launching dnsmasq obtains its data
before going on its usual business.

If we were able to ensure the "data store" (i.e. lease database) were
available on two machines A and B (and up to date on both of course) the
solution would be easy, except for the fact that dnsmasq does not LOOKUP
(i.e. query) for a lease in the data store except upon startup.

I'm thinking along the lines of having a function lease_query() in
lease.c which dnsmasq invokes to determine whether a lease exists before
issuing a new lease for a device.

Being very lightweight, dnsmasq must not be bloated by having a huge
MySQL or other database attached to it. I've been searching the
Internets and finally landed upon Tokyo Tryant [1] which I've discussed a
long time ago [2].

What I'm basically getting at is providing dnsmasq with an optional very
lightweight replicating server which it (optionally) uses to ensure the
lease database can be propagated to a second (or third or fourth)
dnsmasq instance. The reason I'm suggesting Tryant is that, it too, is
lightweight and offers multi-master setups.

     +------------+                       +-------------+
     |   dnsmasq  |                       |  dnsmasq    |
     |     A      |                       |     B       |
     +-----+------+                       +-------------+
           |                                     +
           |                                     |
           |                                     |
     +-----v-------+                      +------v-------+
     |   Tryant    |                      |   Tryant     |
     |     A       |+---------------------&amp;gt;     B        |
     |             |&amp;lt;---------------------+              |
     +-------------+                      +--------------+

     +-------------+                      +---------------+
     |   leases    |                      |    leases     |
     |-------------|                      |---------------|
     +-------------+                      +---------------+

In other words, dnsmasq (A) reads/writes leases from Tryant (A) and
dnsmasq (B) read/writes from/to Tryant (B). If Tryant (A) and (B) can
speak to eachother, the database is replicated, irrespective of which
dnsmasq (A) or (B) has last written a lease.

I'll stop here, before boring you even more, but I'll gladly send you
snippets of code and a short "howto" set up a multi-master system. Most
important IMO is to keep things very light-weight in the spirit of
dnsmasq.

Best regards,

        -JP

[1] http://fallabs.com/tokyocabinet/tokyoproducts.pdf
[2] http://jpmens.net/2009/09/06/tokyocabinet-a-wow-replacement-for-dbm/
&lt;/pre&gt;</description>
    <dc:creator>Jan-Piet Mens</dc:creator>
    <dc:date>2012-05-25T11:17:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5851">
    <title>dnsmasq and sshfp records</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5851</link>
    <description>&lt;pre&gt;Hi List,

I'm currently looking for a solution to provide ssh-keys via DNS. Seems
like sshfp records will solve this issue ... so far so good.
Since we are using dnsmasq as dns/dhcp/pxe-server I wanted to ask how to
put the generated sshfp records into dnsmasq ???
After searching for a while I got only guides for "how to create sshfp
records" or things like "put your sshfp records into dns"....not that
helpful.

Can somebody enlighten me if it is possible to offer ssh keys via dnsmasq,
and how to configure it ?

I tried it similar to the TXT-Records, therefore I created a config-file
sshfp.conf and inserted:
""
myhost SSHFP 1 1 cbe4...c6dc
myhost SSHFP 2 1 20ea...b241
""
But if I want to start dnsmasq I got the error:
""
Starting DNS forwarder and DHCP server: dnsmasq
dnsmasq: bad option at line 1 of /etc/dnsmasq.d/sshfp.conf
 failed!
""


any help appreciated...: Gerd :....
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Gerd Koenig</dc:creator>
    <dc:date>2012-05-24T10:44:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5842">
    <title>Dhcp discover client source ip not 0.0.0.0</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5842</link>
    <description>&lt;pre&gt;Greetings,

I have a Netgear switch that is unable to acquire a DHCP lease. The
DHCP discover request is not replied according to dnsmasq &amp;amp; tcpdump
log. I guess the UDP src ip is a violation of the RFC.

11:26:06.106723 IP (tos 0x0, ttl 64, id 380, offset 0, flags [none],
proto UDP (17), length 281)
   192.168.0.239.68 &amp;gt; 255.255.255.255.67: [udp sum ok] BOOTP/DHCP,
Request from 74:44:01:78:e1:ed, length 253, xid 0x8274d270, Flags
[Broadcast] (0x8000)
         Client-Ethernet-Address 74:44:01:78:e1:ed
         Vendor-rfc1048 Extensions
           Magic Cookie 0x63825363
           DHCP-Message Option 53, length 1: Discover
           MSZ Option 57, length 2: 576
           Parameter-Request Option 55, length 3:
             Subnet-Mask, Default-Gateway, Domain-Name-Server

If I add a route for this IP range on the server the problem is fixed.
sudo route add -net 192.168.0.0 netmask 255.255.255.0 dev vlan20

Shouldn't the broadcast flag in the DHCP request take care of this situation?
Thank you for your assistance.

_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss&amp;lt; at &amp;gt;lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Sen Haerens</dc:creator>
    <dc:date>2012-05-22T10:51:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5838">
    <title>dnsmasq init fails first start on ubuntu 12.04</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5838</link>
    <description>&lt;pre&gt;Hi list,

Im using the 12.04 Ubuntu dnsmasq build (2.59).

If the computer starts, dnsmasq will be started, but no functionality
seemes working.

After killing the dnsmasq-process and restarting the service in this way:

killall dnsmasq
service dnsmasq restart

all runs fine. The configuration is stored in /etc/dnsmasq.conf

Has somebody similar experience and know how to avoid the restart after
boot?

TfH
Oliver
&lt;/pre&gt;</description>
    <dc:creator>Oliver Rath</dc:creator>
    <dc:date>2012-05-21T15:25:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5834">
    <title>dnsmasq-2.61 not responding to ipv6 routersolicitation requests</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5834</link>
    <description>&lt;pre&gt;Hi,

Running dnsmasq-2.61 as just a DNS server and ipv6 router advertisement
daemon, with the following configuration:

domain-needed
bogus-priv
no-dhcp-interface=sixxs
no-dhcp-interface=eth1
no-dhcp-interface=eth0
domain=marienz.net
dhcp-range=2001:610:788::, slaac
enable-ra

it sends periodic router advertisement packets just fine, according to
syslog:

dnsmasq-dhcp[14136]: RTR-ADVERT(br0) 2001:610:788::

and other systems on the network eventually respond to those, but their
router solicitation packets seem to be getting ignored (network traffic
capture did see them arrive on the host dnsmasq runs on, but no response
is sent).

I think this is at least partially caused by a bug in dnsmasq.c: the
main loop only calls icmp6_packet if daemon-&amp;gt;dhcp6 is non-NULL, but
dnsmasq should respond to icmp6 packets if it's providing just RA
services (no dhcpv6) too. That is: I think dnsmasq.c needs something
like this:

diff --git a/src/dnsmasq.c b/src/dnsmasq.c
index 1b951f0..11c2d73 100644
--- a/src/dnsmasq.c
+++ b/src/dnsmasq.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -849,14 +849,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int main (int argc, char **argv)
 }
 
 #ifdef HAVE_DHCP6
-      if (daemon-&amp;gt;dhcp6)
-{
-  if (FD_ISSET(daemon-&amp;gt;dhcp6fd, &amp;amp;rset))
-    dhcp6_packet(now);
+      if (daemon-&amp;gt;dhcp6 &amp;amp;&amp;amp; FD_ISSET(daemon-&amp;gt;dhcp6fd, &amp;amp;rset))
+  dhcp6_packet(now);
 
-  if (daemon-&amp;gt;ra_contexts &amp;amp;&amp;amp; FD_ISSET(daemon-&amp;gt;icmp6fd, &amp;amp;rset))
-    icmp6_packet();
-}
+      if (daemon-&amp;gt;ra_contexts &amp;amp;&amp;amp; FD_ISSET(daemon-&amp;gt;icmp6fd, &amp;amp;rset))
+  icmp6_packet();
 #endif
 
 #  ifdef HAVE_SCRIPT

This brings this bit of code in line with other code in dnsmasq.c that
touches dhcp6fd and icmp6fd. I've also confirmed daemon-&amp;gt;dhcp6 really is
NULL in my problematic dnsmasq instance.

Unfortunately this has not yet made my dnsmasq respond to router
solicitation requests. Is there some known problem I might be hitting?

Thanks,

&lt;/pre&gt;</description>
    <dc:creator>Marien Zwart</dc:creator>
    <dc:date>2012-05-21T13:14:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5832">
    <title>DHCP message</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5832</link>
    <description>&lt;pre&gt;Is it possible to send a message to the client device when an IP address is
allocated via DHCP? This would only be a static info message for my
purposes, and it wouldn't matter much if some clients didn't support
showing it and so ignored it.

Apparently Apple Wi-Fi routers do this, but I'm not sure if this is a
vendor-specific addition or something that other DHCP servers are capable
of too.

Thanks.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Ian Rose</dc:creator>
    <dc:date>2012-05-21T10:34:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5824">
    <title>standard gateway as Forwarding DNS-ip?</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5824</link>
    <description>&lt;pre&gt;Hi list,

my dnsmasq doesnt forward DNS-queries correctly. The goal is, that
dnsmasq takes the standard-gateway of dhcp as forwarding address for
dns-requests. But this didnt work here.

If I put an additional dns-server in /var/run/dnsmasq/resolv.conf, it
runs fine, but this is not the right way, because i dont know at
starttime the name of my standard-gateway.

Whats wrong?

I have a simple configuration here for dnsmasq:
--------------
except-interface=wlan0
dhcp-range=192.168.97.50,192.168.97.150,255.255.255.0,12h
log-queries
--------------

Starting the dnsmasq creates the folloiwing entry in /etc/resolv.conf:
--------------
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
--------------

The server hast the ipadress 192.168.11.254 (eth0) and (should) forward
to 192.168.172.1 via wlan0

--------------
# route -n
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.172.1 0.0.0.0 UG 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
192.168.97.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.172.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
--------------

Now the forwarding is finished by setting forwarding parameter and
Masquerading rule:
--------------
# cat /proc/sys/net/ipv4/ip_forward
1
# iptables -t nat -L
[..]
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- anywhere anywhere
--------------


Here the starting log:
--------------
May 18 13:58:14 dnsmasq[3092]: last message repeated 7 times
May 18 13:58:14 dmi-ThinkPad-T500 dnsmasq[3092]: reading
/var/run/dnsmasq/resolv.conf
May 18 13:58:14 dmi-ThinkPad-T500 dnsmasq[3092]: ignoring nameserver
127.0.0.1 - local interface
May 18 13:58:14 dmi-ThinkPad-T500 dnsmasq[3092]: exiting on receipt of
SIGTERM
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq[3182]: started, version 2.59
cachesize 150
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq[3182]: compile time options:
IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq-dhcp[3182]: DHCP, IP range
192.168.97.50 -- 192.168.97.150, lease time 12h
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq-tftp[3182]: TFTP root is
/opt/dmi/tftproot
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq[3182]: reading
/var/run/dnsmasq/resolv.conf
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq[3182]: ignoring nameserver
127.0.0.1 - local interface
May 18 13:58:16 dmi-ThinkPad-T500 dnsmasq[3182]: /etc/hosts lesen – 7
Adressen
--------------


here an dns-request example:
--------------
May 18 13:59:00 dmi-ThinkPad-T500 dnsmasq[3182]: reading
/var/run/dnsmasq/resolv.conf
May 18 13:59:00 dmi-ThinkPad-T500 dnsmasq[3182]: ignoring nameserver
127.0.0.1 - local interface
May 18 13:59:00 dmi-ThinkPad-T500 dnsmasq[3182]: query[A] heise.de from
192.168.97.73
--------------


Tfh!

Regards
Oliver




_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss&amp;lt; at &amp;gt;lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Oliver Rath</dc:creator>
    <dc:date>2012-05-18T12:09:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5818">
    <title>Need help configuring dhcp stateful IPv6</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5818</link>
    <description>&lt;pre&gt;Hello
I've installed dnsmasq 2.61 on an x86 computer on my LAN. DNS is working fine for A, AAAA, CNAME and PTR records. DHCP for IPv4 is also working.
I have recently began to dabble with IPv6 on my LAN and since I do not yet have a provider for IPv6, I have decided to use RFC 4193 Unique Local (fdxx:) addresses for my LAN. Since I only have a few machines,
 I chose a subnet prefix of /123 and using static IPv6 configuration I was able to ping6 other machines on the same subnet (even by their names), as well as from one subnet to another, even using a sit
 tunnel.
When I set my dhcp-range option in dnsmasq.conf with a prefix-length of 123, I get an "inconsistent DHCPv6 range" error. setting this value to 125 or greater seems to work, also setting it to 120 or less seems to be acceptable to dnsmasq. Checking out my range with an ip calculator didn't reveal any errors (my dynamic ip range is within the same 5-bit subnet).
These are the pertinent bits of my current conf file:dhcp-range=interface:eth0, fdxx:xxxx:xxxx::10, fdxx:xxxx:xxxx::1f, 120, 4henable-ralog-dhcpdhcp-sequential-ip
When I enable networking on a client machine (linux), I see "RTR-SOLICIT(eth0)" messages in the logs, but no responses or advertisements coming from the dnsmasq machine.
I have enabled IPv6 forwarding:# cat /proc/sys/net/ipv6/conf/all/forwarding 1
Please can someone indicate what else I need to check? (I tried using a /64 prefix also, but the results were the same).
ThanksAndre_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Andre Coetzee</dc:creator>
    <dc:date>2012-05-18T08:59:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5816">
    <title>Caching issue question</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5816</link>
    <description>&lt;pre&gt;Hi,
I have a question to the caching of dnsmasq. I installed dnsmasq on 
some of our boxes and configured the boxes to use 127.0.0.1 in 
/etc/resolv.conf (so they use dnsmasq). That works really well and I can 
resolve DNS queries on those boxes. All the queries get send from 
dnsmasq to our internal DNS server (which has internal zones 
configured). For testing I checked the incoming DNS requests on the 
central DNS server with the usage of "dnscap". I encountered a strange 
thing:

When I do a "dig session-storage.fd.corp" (fd.corp is an internal 
domain) the first time on one box where dnsmasq is installed I can see 
that one requests comes in on the central DNS server. The second time I 
execute it, nothing comes in on the central DNS. So it gets cached in 
dnsmasq which is fine. The problem appears when I do a "dig 
session-storage.fd.corp" and a "dig AAAA session-storage.fd.corp" 
alternately. I can see an incoming request for every dig request on the 
central DNS server which means that there is no caching. I enabled 
logging in dnsmasq and it seems that a request to the AAAA address 
overwrites the cache entry for the A request. There is no AAAA entry on 
our DNS server for session-storage.fd.corp (only an "A" entry is there 
and this is a CNAME).

So my question is if this is a normal behaviour of dnsmasq or a bug? I 
have a php application which requests those A and AAAA names alternately 
(this is how I recognized it).

I am running dnsmasq 2.59 (the version from Ubuntu 12.04). Our central 
DNS server uses powerdns.


Thanks for your help in advance.


Best Regards
Nick
&lt;/pre&gt;</description>
    <dc:creator>Nick</dc:creator>
    <dc:date>2012-05-18T08:14:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5804">
    <title>vim highlighting for dnsmasq</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5804</link>
    <description>&lt;pre&gt;Hello

i am the author of the vim syntax file for dnsmasq:
https://vim.googlecode.com/hg/runtime/syntax/dnsmasq.vim

Currently i am in the process of updating it for 2.61 and have a question
regarding whether it is allowed for comments starting in the middle of the line.
The manpage says "Lines  starting with  # are comments and ignored." Does this
mean comments *must* start at the line beginning?

&lt;/pre&gt;</description>
    <dc:creator>Thilo Six</dc:creator>
    <dc:date>2012-05-17T13:12:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5795">
    <title>Option name in Dnsmasq and OpenWrt</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5795</link>
    <description>&lt;pre&gt;Hello,

I found a difference between options name in the man page of Dnsmasq and
the options described in the documentation of OpenWRT about Dnsmasq.
So, i don't know what to use for example: to configure a dhcp range in dhcp
config file on OpenWrt we use:

config 'dhcp' 'lan'
          option 'interface' 'lan'
          option 'start' '62'
          option 'limit' '192'
          option 'leasetime' '600h'

Or we use:

config 'dhcp' 'lan'
          option 'dhcp_range' '10.22.0.1,10.22.0.254,600h'
          option 'lease-max' '192'


thanks.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>dnsmasq dnsmasq</dc:creator>
    <dc:date>2012-05-16T09:50:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5787">
    <title>[PATCH] Support dbus activation</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5787</link>
    <description>&lt;pre&gt;Introduce dbus service file and turn dbus on in the systemd
unit.

Note to packagers:
To add support for dbus activation, you must install the dbus
service file (dbus/uk.org.thekelleys.dnsmasq.service) into
$DATADIR/dbus-1/system-services.

---
 contrib/systemd/dnsmasq.service        |    2 +-
 dbus/uk.org.thekelleys.dnsmasq.service |    7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)
 create mode 100644 dbus/uk.org.thekelleys.dnsmasq.service

diff --git a/contrib/systemd/dnsmasq.service 
b/contrib/systemd/dnsmasq.service
index a27fe6d..4a784d3 100644
--- a/contrib/systemd/dnsmasq.service
+++ b/contrib/systemd/dnsmasq.service
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -5,7 +5,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; Description=A lightweight DHCP and caching DNS server
 Type=dbus
 BusName=uk.org.thekelleys.dnsmasq
 ExecStartPre=/usr/sbin/dnsmasq --test
-ExecStart=/usr/sbin/dnsmasq -k
+ExecStart=/usr/sbin/dnsmasq -k -1
 ExecReload=/bin/kill -HUP $MAINPID
 
 [Install]
diff --git a/dbus/uk.org.thekelleys.dnsmasq.service 
b/dbus/uk.org.thekelleys.dnsmasq.service
new file mode 100644
index 0000000..f5fe98d
--- /dev/null
+++ b/dbus/uk.org.thekelleys.dnsmasq.service
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -0,0 +1,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
+[D-BUS Service]
+Name=uk.org.thekelleys.dnsmasq
+Exec=/usr/sbin/dnsmasq -k -1
+User=root
+SystemdService=dnsmasq.service
+
+
&lt;/pre&gt;</description>
    <dc:creator>Alex Elsayed</dc:creator>
    <dc:date>2012-05-15T08:53:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5786">
    <title>Patch: Add --ping-timeout option</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5786</link>
    <description>&lt;pre&gt;Hello,

This is a patch I wrote for dnsmasq to allow changing the timeout on the
ping
request sent to an IP address to determine whether the address is free
to give
out to a DHCPv4 client. The default value according to the manpage was
1.5
seconds and not changeable. This option lets you set the timeout to a
number of
milliseconds.

I noticed that I had to multiply the given timeout by 2 in order for it
to wait
the correct amount of time. This is reflected in the PING_WAIT constant
as
well, which was set to 3 in order to wait 1.5 seconds. While I believe
my patch
is performing correct behavior, I'd appreciate some explanation as to
why this
is necessary.

I've placed a maxmimum limit of 15 seconds on the timeout. This is
because it
appears that PING_CACHE_TIME must be greater than the timeout. See the
patch
made in dhcp.c for the area where this issue is of concern. 

I have attached the output of `git diff` to this email as a patch. If
this is
not the correct format, please let me know.

Aaron Opfer
diff --git a/man/dnsmasq.8 b/man/dnsmasq.8
index 0a3b5df..cc2229e 100644
--- a/man/dnsmasq.8
+++ b/man/dnsmasq.8
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1073,6 +1073,16 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; ICMP echo request (aka "ping") to the address in question. If it gets
 a reply, then the address must already be in use, and another is
 tried. This flag disables this check. Use with caution.
 .TP
+.B --ping-timeout=&amp;lt;milliseconds&amp;gt;
+(IPv4 only) Specifies how long to wait for an ICMP echo reply from an IP address
+before dnsmasq considers it free to be allocated to a host. By default, unless
+--no-ping is used, this is 1.5 seconds. It might be safe to lower this on low-latency
+networks. The maximum value is 15 seconds. Another use is for redundant primary/secondary 
+dnsmasq servers, in lieu of true cooperative load-sharing; setting the primary server
+ to have a lower ping-timeout than the secondary would cause the primary server 
+to answer most requests first. Adding --dhcp-authoritative to the primary server
+would also help this.
+.TP
 .B --log-dhcp
 Extra logging for DHCP: log all the options sent to DHCP clients and
 the tags used to determine them.
diff --git a/src/config.h b/src/config.h
index 84025f7..7faadd2 100644
--- a/src/config.h
+++ b/src/config.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -26,7 +26,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 #define LEASE_RETRY 60 /* on error, retry writing leasefile after LEASE_RETRY seconds */
 #define CACHESIZ 150 /* default cache size */
 #define MAXLEASES 1000 /* maximum number of DHCP leases */
-#define PING_WAIT 3 /* wait for ping address-in-use test */
+#define PING_WAIT 3000 /* wait for ping address-in-use test */
 #define PING_CACHE_TIME 30 /* Ping test assumed to be valid this long. */
 #define DECLINE_BACKOFF 600 /* disable DECLINEd static addresses for this long */
 #define DHCP_PACKET_MAX 16384 /* hard limit on DHCP packet size */
diff --git a/src/dhcp.c b/src/dhcp.c
index 045eb3a..0fb1671 100644
--- a/src/dhcp.c
+++ b/src/dhcp.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -630,7 +630,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int address_allocate(struct dhcp_context *context,
       {
 struct ping_result *r, *victim = NULL;
 int count, max = (int)(0.6 * (((float)PING_CACHE_TIME)/
-      ((float)PING_WAIT)));
+      (daemon-&amp;gt;ping_timeout*2/1000.0f)));
 
 *addrp = addr;
 
diff --git a/src/dnsmasq.c b/src/dnsmasq.c
index 1b951f0..475d811 100644
--- a/src/dnsmasq.c
+++ b/src/dnsmasq.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1486,7 +1486,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int icmp_ping(struct in_addr addr)
  retry_send());
   
   for (now = start = dnsmasq_time(); 
-       difftime(now, start) &amp;lt; (float)PING_WAIT;)
+       difftime(now, start) &amp;lt; (daemon-&amp;gt;ping_timeout*2/1000.0f);)
     {
       struct timeval tv;
       fd_set rset, wset;
diff --git a/src/dnsmasq.h b/src/dnsmasq.h
index 445efad..0064902 100644
--- a/src/dnsmasq.h
+++ b/src/dnsmasq.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -812,6 +812,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; extern struct daemon {
   struct iovec dhcp_packet;
   char *dhcp_buff, *dhcp_buff2, *dhcp_buff3;
   struct ping_result *ping_results;
+  int ping_timeout;
   FILE *lease_stream;
   struct dhcp_bridge *bridges;
 #ifdef HAVE_DHCP6
diff --git a/src/option.c b/src/option.c
index 5cb7d7b..0531e77 100644
--- a/src/option.c
+++ b/src/option.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -118,6 +118,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; struct myoption {
 #define LOPT_DUID      307
 #define LOPT_HOST_REC  308
 #define LOPT_TFTP_LC   309
+#define LOPT_PING_TO   310
 
 #ifdef HAVE_GETOPT_LONG
 static const struct option opts[] =  
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -185,6 +186,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static const struct myoption opts[] =
     { "bootp-dynamic", 2, 0, '3' },
     { "dhcp-mac", 1, 0, '4' },
     { "no-ping", 0, 0, '5' },
+    { "ping-timeout",1, 0, LOPT_PING_TO },
     { "dhcp-script", 1, 0, '6' },
     { "conf-dir", 1, 0, '7' },
     { "log-facility", 1, 0 ,'8' },
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -328,6 +330,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static struct {
   { '4', ARG_DUP, "set:&amp;lt;tag&amp;gt;,&amp;lt;mac address&amp;gt;", gettext_noop("Map MAC address (with wildcards) to option set."), NULL },
   { LOPT_BRIDGE, ARG_DUP, "&amp;lt;iface&amp;gt;,&amp;lt;alias&amp;gt;..", gettext_noop("Treat DHCP requests on aliases as arriving from interface."), NULL },
   { '5', OPT_NO_PING, NULL, gettext_noop("Disable ICMP echo address checking in the DHCP server."), NULL },
+  { LOPT_PING_TO, ARG_ONE, "&amp;lt;milliseconds&amp;gt;", gettext_noop("Timeout for ICMP echo reply in the DHCP server."), NULL },
   { '6', ARG_ONE, "&amp;lt;path&amp;gt;", gettext_noop("Shell script to run on DHCP lease creation and destruction."), NULL },
   { LOPT_LUASCRIPT, ARG_DUP, "path", gettext_noop("Lua script to run on DHCP lease creation and destruction."), NULL },
   { LOPT_SCRIPTUSR, ARG_ONE, "&amp;lt;username&amp;gt;", gettext_noop("Run lease-change scripts as this user."), NULL },
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1353,6 +1356,16 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static char *one_opt(int option, char *arg, char *gen_prob, int command_line)
         daemon-&amp;gt;lease_change_command = opt_string_alloc(arg);
 #  endif
       break;
+
+    case LOPT_PING_TO: /* --ping-timeout */
+      if(!atoi_check(arg,&amp;amp;daemon-&amp;gt;ping_timeout))
+        option = '?';
+      else if ( daemon-&amp;gt;ping_timeout &amp;gt; 15000  )
+        problem = _("ping-timeout must be less than 15 seconds (15000 milliseconds)");
+      else if ( daemon-&amp;gt;ping_timeout &amp;lt;= 0 )
+        problem = _("ping-timeout must be greater than 0");
+      break;
+
 #endif /* HAVE_DHCP */
 
     case LOPT_DHCP_HOST: /* --dhcp-hostfile */
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -3525,6 +3538,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; void read_opts(int argc, char **argv, char *compile_opts)
   daemon-&amp;gt;tftp_max = TFTP_MAX_CONNECTIONS;
   daemon-&amp;gt;edns_pktsz = EDNS_PKTSZ;
   daemon-&amp;gt;log_fac = -1;
+  daemon-&amp;gt;ping_timeout = PING_WAIT;
   add_txt("version.bind", "dnsmasq-" VERSION );
   add_txt("authors.bind", "Simon Kelley");
   add_txt("copyright.bind", COPYRIGHT);
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>aopfer-iaspzbLtXqSWZO0wgtXLWFaTQe2KTcn/&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-14T18:04:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5784">
    <title>НА: dnsmasq 2.61 no periodic RA's and sendto errors</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5784</link>
    <description>&lt;pre&gt;Jim, make sure you're using enable-ra in your config

Best regards, Vladislav Grishenko

----- Reply message -----
От: "Jim Bos" &amp;lt;jim876&amp;lt; at &amp;gt;xs4all.nl&amp;gt;
Кому: "Simon Kelley" &amp;lt;simon&amp;lt; at &amp;gt;thekelleys.org.uk&amp;gt;
Копия: "Vladislav Grishenko" &amp;lt;themiron&amp;lt; at &amp;gt;mail.ru&amp;gt;, &amp;lt;dnsmasq-discuss&amp;lt; at &amp;gt;lists.thekelleys.org.uk&amp;gt;
Тема: dnsmasq 2.61 no periodic RA's and sendto errors
Дата: вс, май 13, 2012 22:29


On 05/12/2012 04:34 PM, Simon Kelley wrote:

I tried the patches already but unfortunately still don't get RA's. But
note I'm using SLAAC-only and the patch seem to be for non-slaac cases.
 I'll see if I can try an almost empty config file on another PC to
exclude any specific problem on my router.

=
Jim

_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Vladislav Grishenko</dc:creator>
    <dc:date>2012-05-13T18:15:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5779">
    <title>dnsmasq 2.61 no periodic RA's and sendto errors</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5779</link>
    <description>&lt;pre&gt;Hi Simon,

dnsmasq 2.61 has couple of issues:
1. No Router Advertisement and corresponding syslog sendto error when
replying on Router Solicitation from Windows XP and possible other OSes
It's caused by absence of source IPv6 address in RS packet, what is allowed
by RFC if host's interface doesn't acquired valid link-local yet
In this case RA should be sent to all nodes multicast address (sources has
ALL_HOSTS define, which has a bit different meaning)
2. For non-slaac modes periodic RA doesn't work because next RA event could
be reset by empty next slaac event
Actually it could work only for the first time, if additional random delay
is 0.

Patches attached.

Best Regards, Vladislav Grishenko


_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>Vladislav Grishenko</dc:creator>
    <dc:date>2012-05-11T14:16:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5777">
    <title>Multiple IP blocks on single ethernet segment</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5777</link>
    <description>&lt;pre&gt;Guys - I've dug through the list archives and I haven't seen a clear answer
to this, so excuse me if I'm repeating things.

I'm running dnsmasq for DHCP services (as part of CloudStack). IP addresses
are statically assigned via mac, defined in /etc/dhcphosts.txt. This all
works perfectly fine for a single IP block.

Until I try to assign IPs for another IP block, and then get


May 10 01:28:49 dnsmasq-dhcp[1057]: no address range available for DHCP
request via eth0


Problem is, when I order IP blocks from my provider, they're routed to me
via my VLAN. I have multiple /28s on this single Ethernet segment. I need
dnsmasq to be able to answer DHCP requests to Ethernet addresses with IP
addresses that are outside the network range of the listening interface.

My understanding is this is a limitation in dnsmasq?

On the DHCP side, I can't think of a technical limitation that causes this
- DHCP is a layer 3 protocol, it doesn't care about IP ranges on
interfaces. I'm presuming this limitation is in place because of the DNS
caching side of the equation?

If I'm completely wrong and dnsmasq (version 2.55) does support this, my
apologies and I'd appreciate a pointer in the right direction.

John
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
&lt;/pre&gt;</description>
    <dc:creator>John Kinsella</dc:creator>
    <dc:date>2012-05-10T20:07:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5775">
    <title>dnsmasq and multicast (224.0.0.12)</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5775</link>
    <description>&lt;pre&gt;
Please forgive the newbie question.

Is there anything in dnsmasq which implements listening on a
multicast address?  The IANA address allocation does say that
224.0.0.12 is a standard DHCP server address, on which I assume DHCP
servers can listen.

First: is this even a responsibility of this application layer of
the stack, or is it supposed to be implemented in kernel or network
configuration?

Second: the end goal is to have multiple dnsmasq-based DHCP servers
listening on not-well-known IP addresses on the network.  Also, the
servers should only receive requests from a proprietary relay agent,
which won't know the IP address of the DHCP servers.  I think
multicast is the way to solve this, but I'm not positive.  Any ideas?


&lt;/pre&gt;</description>
    <dc:creator>David Dombrowsky</dc:creator>
    <dc:date>2012-05-09T20:00:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5771">
    <title>DHCP Option 12 (Hostname) problem</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5771</link>
    <description>&lt;pre&gt;
Dear DNSMASQ'ers

I am developing code for an embedded micro controller with
a network interface.

I am presently working on the DCHP client code where dnsmasq
is both name server and dhcp server.  The dnsmasq OS environment
is OpenBSD, although I doubt the OS is a factor here.

While I am by no means new to network programming, I have
never actually written code to make DHCP happen before so
I am learning new details as I go.

I am considering how to handle the case where the client
(my controller) asks for a specific hostname in its DISCOVER
and REQUEST messages and I know that specific name is not
available because it is committed to an unexpired leaseholder.

In no case is dnsmasq responding to my client's option 12
in its OFFER or ACK messages.  By that I mean, in cases of
a clear name being requested or in cases where the requested
name is in conflict with an already committed name, I see
nothing from dnsmasq on option 12.

In cases where the name does not conflict, the DNS side of
dnsmasq will resolve the requested name correctly.

The only unusual dnsmasq thing is I am restricting the IP
address range for my controllers as shown:

     dhcp-range=tag:nburn,192.168.10.150,192.168.10.165,1h
     dhcp-mac=set:nburn,00:03:f4:*:*:*

I admit I have not tested against any other DNS/DHCP servers
and I don't want to bring up the ISC bind/dhcp atrocity
just to get another data point.

I'm wishing some kind soul can slap me with a clue stick,
for which I will be most grateful.  I can and will happily
supply actual logs, configs and wire transcripts if needed.

I'm hoping I've overlooked something and its only me that
needs debugging and not dnsmasq.

Regards,
Ray
&lt;/pre&gt;</description>
    <dc:creator>Raymond Lillard</dc:creator>
    <dc:date>2012-05-09T01:57:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5764">
    <title>strange list server bounces</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5764</link>
    <description>&lt;pre&gt;Hello,

A problem of some sort exists with the list
server configuration.  All messages submitted
from here bounce when relayed by a mature
'sendmail' configuration.  Only way to submit
messages is manually using 'nc' directly to
one of the MX servers.  Bounce message example
follows.


The original message was received at Tue, 8 May 2012 11:05:36 -0400
from ciannait [172.29.87.10]

   ----- The following addresses had permanent fatal errors -----
&amp;lt;dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
    (reason: 550 Unrouteable address)

   ----- Transcript of session follows -----
.. while talking to ipv6.thekelleys.org.uk.:
&amp;lt;&amp;lt;&amp;lt; 550 Unrouteable address
550 5.1.1 &amp;lt;dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org&amp;gt;... User unknown
&amp;lt;&amp;lt;&amp;lt; 503-All RCPT commands were rejected with this error:
&amp;lt;&amp;lt;&amp;lt; 503-Unrouteable address
&amp;lt;&amp;lt;&amp;lt; 503 Valid RCPT command must precede DATA

Reporting-MTA: dns; mx.binnacle.cx
Received-From-MTA: DNS; ciannait
Arrival-Date: Tue, 8 May 2012 11:05:36 -0400

Final-Recipient: RFC822; dnsmasq-discuss-xn1N/tgparsycpQjotevgVpr/1R2p/CL&amp;lt; at &amp;gt;public.gmane.org
Action: failed
Status: 5.1.1
Remote-MTA: DNS; ipv6.thekelleys.org.uk
Diagnostic-Code: SMTP; 550 Unrouteable address
Last-Attempt-Date: Tue, 8 May 2012 11:06:02 -0400

Return-Path: &amp;lt;starlight-Utvwg/EOxnhfq8cQ1yknNg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Received: from CIANNAIT.binnacle.cx (ciannait [172.29.87.10])
by mx.binnacle.cx (envelope-from &amp;lt;starlight-Utvwg/EOxnhfq8cQ1yknNg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;)
(8.14.4/8.14.4) with ESMTP id q48F5ZC3000434
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for &amp;lt;dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj&amp;lt; at &amp;gt;public.gmane.org&amp;gt;; Tue, 8 May 2012 11:05:36 -0400
Message-Id: &amp;lt;6.2.5.6.2.20120508110522.05b99158-Utvwg/EOxnhfq8cQ1yknNg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 May 2012 11:05:34 -0400
To: dnsmasq-discuss-xn1N/tgparsycpQjotevgVpr/1R2p/CL&amp;lt; at &amp;gt;public.gmane.org
From: starlight-Utvwg/EOxnhfq8cQ1yknNg&amp;lt; at &amp;gt;public.gmane.org
Subject: test
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Received-SPF: pass (mx.binnacle.cx: 172.29.87.10 is whitelisted by SPF-milter whitelist entry)

test
&lt;/pre&gt;</description>
    <dc:creator>starlight-Utvwg/EOxnhfq8cQ1yknNg&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-08T15:15:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5762">
    <title>dnsmasq unresponsive to /etc/hosts queries duringWAN network outages</title>
    <link>http://comments.gmane.org/gmane.network.dns.dnsmasq.general/5762</link>
    <description>&lt;pre&gt;Running 'dnsmasq' 2.57 on a CentOS server here
rather than on a router.

Whenever the WAN link goes down, usually for
maintenance by the service provider, 'dnsmasq'
stops responding to local /etc/hosts queries
along with wide-area queries.  This has the
effect of preventing numerous local activities
from functioning, including 'telnet', 'ssh',
and local 'sendmail' messaging.

Is there any way to configure 'dnsmasq' so
that it will respond timely to such queries
even when all remote DNS servers are not
responding?

The current configuration follows below.
No command-line options are passed during
startup.

Thank you for your help.



cache-size=10000
no-resolv
server=2001:470:20::2
domain-needed
dhcp-authoritative
dhcp-leasefile=/tmp/dhcp.leases
dhcp-option=44,172.29.87.19
dhcp-range=172.29.87.100,172.29.87.149,255.255.255.0,12h
dhcp-range=172.29.88.100,172.29.88.149,255.255.255.0,12h
read-ethers
&lt;/pre&gt;</description>
    <dc:creator>starlight-Utvwg/EOxnhfq8cQ1yknNg&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-08T14:49:38</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.dns.dnsmasq.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.dns.dnsmasq.general</link>
  </textinput>
</rdf:RDF>

