Thanks for your reply, I have tested further and
it certainly looks like dnsmasq does not handle multiple A records with the
same name like domaindnszones.mydomain.foo (resolves to 36 ip-adresses)
and forestdnszones.mydomain.foo (resolves to 36 ip-adresses) that good
We use dnsmasq 2.48 (RHEL
Hello Erling,
2.48 is getting quite old, and i remember having
encountered issues when first deploying the EL6 version.
I've moved to
newer versions long time ago and use dnsmasq in production in front of
AD servers. I definitely can't reproduce that behaviour on 2.70, see
below:
# dig
Long time dnsmasq user here, It's a great product, and we're using it on a
mid-sized network of 200+ hosts.
Our business is to the point where we need to eliminate single points of
failure to protect business continuity.
I've looked through the archives and dnsmasq failure is a frequent topic of
Hi,
Sorry for bringing up such an old thread but I was circling back onto this
problem and I wonder if we could revisit it.
On 17/09/14 09:49, Joachim Nilsson wrote:
Hi Simon,
I've found a little problem with how Option 82 circuit-id/remote-id
works. Everything is fine in the below setup
