Comment 52 for bug 1639776

@exander77 there is no need for personal abuse here. In that case the description of this bug should have been updated to include that. However I see there is debate on that bug about whether it is fixed by the version of dnsmasq which fixes this bug. If not then it is definitely a different bug. I suggest opening a new bug. It will not get duplicated to this one if the dnsmasq fix does not fix the problem. There is no point commenting further on this bug as it is marked as fixed so no-one will do anything about it.