[Dnsmasq-discuss] Problems using 'split horizon' approach

[Dave Ewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday, 22.08.2005 at 12:19 +0100, Simon Kelley wrote:

> >$ host apollo
> >apollo.ceu.ox.ac.uk has address 10.99.0.2
> >$ host -t any apollo
> >apollo.ceu.ox.ac.uk has address 163.1.168.2
> >$ host apollo
> >apollo.ceu.ox.ac.uk has address 10.99.0.2
> >apollo.ceu.ox.ac.uk has address 163.1.168.2
> >
> >etc.
> >
> >The tcpdump shows that during the 'any' request, the dnsmasq host cannot
> >serve it (presumably because it only has an 'A' record?) and the request
> >is forwarded to the upstream DNS server, which returns the public IP,
> >which then gets included in the cache.
> >
> >Is this the expected behaviour of dnsmasq in these circumstances?
> >
> 
> Did we ever establish which version you are using? ISTR that you are 
> using Debian "woody", and maybe therefore the very old 1.4 dnsmasq 
> release. If that's the case, then yes, I would expect that behaviour, 
> and the fix it to upgrade to dnsmasq 2.22 in "sarge". If you are using 
> dnsmasq 2.22 then I'm very interested, since this problem was long ago 
> thought to be fixed in the 2.x series.
> 
> If needs be the Debian dnsmasq-2.22_2 package will build from source and 
> run quite successfully on a Woody system.

My apologies.  I did build dnsmasq from the 2.22 source, but it appears
it failed to install properly.

After properly installing it, the above described behaviour does not
appear to re-occur.

Thanks Simon ...

Dave.
- -- 
Dave Ewart
davee at ceu.ox.ac.uk
Computing Manager, Cancer Epidemiology Unit
Cancer Research UK / Oxford University
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
N 51.7518, W 1.2016
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDCbdJbpQs/WlN43ARAouAAKD08BJpKUmUsc0M44IWRKo5KCxBOQCfdLe5
7kKqzQ/pl+PSws1DHSBlp60=
=bYdJ
-----END PGP SIGNATURE-----