or if you prefer less typing "ss -lnp | grep -w 53".
Rather than doing external filtering, you can also use the ipfilter
baked-in syntax:
ss -lnp 'sport = :53'
(listening, hence "source port" notion is reversed)
(you could also append -t or -u options to filter repectively on TCP or
UDP if th
Στις 17/4/21 1:36 π.μ., ο/η Ralph
Ronnquist via Dng έγραψε:
In order to determine which process if any is listening on port 53
(the registered DNS port) do, as root, "netstat -lnp | grep -w 53",
or if you prefer less typing "ss -lnp | grep -w 53".
another one :
`lsof -i :53`
OpenPGP_signat
On Fri, 16 Apr 2021 18:24:23 -0400
Hendrik Boom wrote:
> Hers's the /etc/resolv.conf on my davuan buster laptop:
>
> # Generated by Connection Manager
> nameserver ::1
> nameserver 127.0.0.1
>
> Now I have no problem resolving domain names, whither in chromium,
> firefox-esr, or even just ping
On Sat, Apr 17, 2021 at 12:24 AM Hendrik Boom
wrote:
> How should I find just how dns lookup is done on my machine,
> and how should it be done?
>
>
maybe :
netstat -nap | grep 53
it should show you something like :
tcp0 0 0.0.0.0:22556 0.0.0.0:* LISTEN
Hers's the /etc/resolv.conf on my davuan buster laptop:
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1
Now I have no problem resolving domain names, whither in chromium,
firefox-esr, or even just ping.
But a far as I know, I have never put a dns esolver on the laptop.
Do
