[Dnsmasq-discuss] Finding actual DNS server used

[David Forrest]

I just run the host command on a questionable resolution target with a
defined dns and compare it with with the default (which should be 127.0.0.1
in my case: as I do have a bunch of undesirables in my hosts file resolving
to the loopback per: http://someonewhocares.org/hosts/).

drf at raspberrypi:~ $ host cyberscat.com
cyberscat.com has address 127.0.0.1
cyberscat.com has IPv6 address ::1
drf at raspberrypi:~ $ host cyberscat.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

cyberscat.com has address 69.162.80.55
drf at raspberrypi:~ $

Amicalement,
Dave F.


On Sat, Jan 14, 2017 at 4:43 PM, Jim Alles <kb3tbx at gmail.com> wrote:

> Lars,
>
> On Sat, Jan 14, 2017 at 7:40 AM, Lars Noodén <lars.nooden at gmail.com>
> wrote:
>
>> How can I get an already running instance of Dnsmasq to tell which DNS
>> servers it is using to resolve new queries upstream?
>>
>> ​I am not sure that is the most reliable way to get the information you
> are looking for.​ Any client App can try to use whatever DNS server it
> wants to resolve names. That isn't polite, but it happens a lot with
> smartphones, and IoT in general.
>
> As far as the desktop OS, a user can override the DNS entries that DHCP
> provides.
>
> I lock my network clients into OpenDNS by using dnsmasq on my router
> (Untangle's NGFW) pointed to their servers, and the firewall to block any
> other attempts besides dnsmasq. The firewall then provides a handy log of
> attempts to bypass my wishes.
>
> Another way to see what is going on, is to run wireshark and filter for
> UDP port 53.
>
> dnsmasq can't know about things going around it.
>
> Peace,
>
> Jim A.
>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20170114/2c3aef61/attachment.html>