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
da...@ceu.ox.ac.uk
Computing Manager, Cancer Epidemiology Unit
Cancer
in the cache.
Is this the expected behaviour of dnsmasq in these circumstances?
Dave.
- --
Dave Ewart
da...@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
' by information from
the upstream DNS, but what I don't understand is why that server is even
*consulted* for a host which exists in the local /etc/hosts ...
Can anyone shed any light on what's going on here?
Dave.
- --
Dave Ewart
da...@ceu.ox.ac.uk
Computing Manager, Cancer Epidemiology Unit
Cancer Research
are making this happen.
The reason you are seeing the two addresses alternate is so that
load-balancing via DNS will work - the order in which multiple A records
for the same domain get returned is permuted on every cache lookup.
That makes sense and is as I suspected ...
Cheers,
Dave.
- --
Dave
