Package: dnsmasq Version: 2.20-1 Severity: important
polaris:~# ping tov.uwcs.co.uk PING tov.uwcs.co.uk (1.0.0.0): 56 data bytes [...] polaris:~# /etc/init.d/dnsmasq force-reload Restarting DNS forwarder and DHCP server: dnsmasq. polaris:~# ping tov.uwcs.co.uk PING molotov.uwcs.co.uk (137.205.210.240): 56 data bytes [...]
This has happened a couple of times earlier today; both times doing a force-reload fixed it immediately.
polaris:~# egrep -v '^#|^$' /etc/dnsmasq.conf domain-needed bogus-priv filterwin2k no-resolv no-poll server=192.168.6.254 server=62.241.162.200 server=62.241.160.200 expand-hosts domain=galaxy.org.uk
How confident are you about the upstream DNS servers which dnsmasq is talking to? What you saw could be explained if an earlier query for the same name got a 1.0.0.0 answer from an upstream server which was then cached by dnsmasq.
In particular, is the server 192.168.6.254 some sort of ADSL router or similar? A quick google on "DNS 1.0.0.0" gives some tantalising clues that this might be a bug that's lurking in the firmware of some of those.
"1.0.0.0" is not used as an invalid or sentinel value anywhere in the dnsmasq code, so if the bug is truly a dnsmasq one, I don't have much of a handle on where it might be.
Cheers,
Simon.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
