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
On 2020-11-03 02:36, Steve Litt wrote:
> When it comes to separation of authoritative and resolver parts of DNS,
> the documentation from the old djbdns makes it very clear, and is an
> excellent starting point.
I have just acted on this as well, and now authoritative answers for my
domain are se
Quoting Steve Litt (sl...@troubleshooters.com):
> Yes, and I think that's outdated.
You can configure your DHCP client software to _not_ use nameserver IPs
sent by the DHCPd and instead use locally defined ones. If using
ISC's dhclient, set
supersede domain-name-servers ip-address [, ip-addre
On Thu, 11 Jul 2019 20:07:05 -0700
Rick Moen wrote:
> http://connectman.sourceforge.net/
CLI connection manager looks pretty cool, especially if I can team it
up with UMENU. I might try it out as a substitute for using wpa_gui and
wpa_password.
SteveT
Steve Litt
July 2019 featured book: Troub
On Thu, 11 Jul 2019 22:14:45 -0400
Hendrik Boom wrote:
> On Thu, Jul 11, 2019 at 08:34:59PM -0400, Steve Litt wrote:
> > Hi Hendrik,
> >
> > It isn't just conman: It's all these silly "we do it all for you"
> > networking helpers. I just do this:
> >
> > chattr +i /etc/resolv.conf
> >
> > Unt
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> Does conman, the connection manager, originate from Helpful Lennart?
Nei.
http://connectman.sourceforge.net/
> And doesn't the DNS IP number on a mobile device like a laptop normally
> come from the DHCP protocol?
Pretty nearly universally, ja.
On Thu, Jul 11, 2019 at 08:34:59PM -0400, Steve Litt wrote:
> On Wed, 10 Jul 2019 11:31:31 -0400
> Hendrik Boom wrote:
>
> > This morning DNS wasn't working on my laptop, though it worked
> > perfectly well on the server it wifi-ed to.
> > After some pinging and checking connections, I found this
On Wed, 10 Jul 2019 11:31:31 -0400
Hendrik Boom wrote:
> This morning DNS wasn't working on my laptop, though it worked
> perfectly well on the server it wifi-ed to.
> After some pinging and checking connections, I found this on my
> laptop.
>
> The file /etc/resolv.conf:
>
> # Generated by Co
Quoting Dimitris via Dng (dng@lists.dyne.org):
> maybe it expects you to run a local caching dns resolver :D
The best (IMO) term for what you're describing is 'recursive server',
though there's a lot of variant word usage.
https://en.wikipedia.org/wiki/Domain_Name_System#Recursive_and_caching_nam
I'm using connman too! :(
I just updated mine /etc/resolv to
nameserver 8.8.8.8
nameserver 8.8.4.4
and it was instantly changed to
nameserver 209.222.18.222
nameserver 209.222.18.218
Ozi
On Thu, Jul 11, 2019 at 1:31 AM Hendrik Boom wrote:
> This morning DNS wasn't working on my laptop, tho
On 7/10/19 6:31 PM, Hendrik Boom wrote:
> Now why would the connection manager (conman) suddenly be setting my
> nameserver to localhost?
maybe it expects you to run a local caching dns resolver :D
it might actually provide a faster experience... using
unbound/dnsmasq/others. wiki.archlinux.org
https://manpages.debian.org/stretch/connman/connman.8.en.html
Look at the -r option. Maybe that lets you disable the built-in DNS proxy. Was
that previously set somewhere?
> On 11 Jul 2019, at 01:31, Hendrik Boom wrote:
>
> This morning DNS wasn't working on my laptop, though it worked perfect
This morning DNS wasn't working on my laptop, though it worked perfectly
well on the server it wifi-ed to.
After some pinging and checking connections, I found this on my
laptop.
The file /etc/resolv.conf:
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1
Now why would the
The original compiles and runs on my Devuan Jessie system.
Source: https://cr.yp.to/djbdns/djbdns-1.05.tar.gz
Instructions: https://cr.yp.to/djbdns/install.html
On 02/22/2018 04:22 PM, John Crisp wrote:
> Hi,
>
> looking for a little advice.
>
> Have spun up a small Devuan instance for a open
Hi,
looking for a little advice.
Have spun up a small Devuan instance for a openvpn server for a friend.
I built a similar system for myself some while back in CentOS 6 and used
ndjbdns for tinydns and dnscache.
That has worked well and I wanted to replicate that to Devuan but...
no ndjbdns
You can setup lightttpd and use a host file as well (use unbound on
embedded).
Create an "empty" html document on the server:
in index.htm:
I found this works better than using transparent gifs, pop ups are
killed too.
On Monday, March 13, 2017 8:11 PM, Patrick Meade
wrote:
On 03/1
On 03/13/2017 02:46 PM, Rob van der Putten wrote:
On 12/03/17 16:49, Renaud (Ron) OLGIATI wrote:
Have you considered rolling your own add-blocking with a list of
unwanted sites in /etc/hosts ?
A bad idea, because your browser expects some sort of response.
It's better to replace unwanted con
On Mon, 15 Aug 2016 07:12:02 -0400
Hendrik Boom wrote:
> On Mon, Aug 15, 2016 at 03:25:01AM -0700, Rick Moen wrote:
> >
> > There shouldn't IMO be broken DNS any more on modern networked *ix
> > hosts. Run a local recursive resolver and list 127.0.0.1 as the
> > first resolv.conf entry. It's
On Mon, 15 Aug 2016 07:12:02 -0400
Hendrik Boom wrote:
> > There shouldn't IMO be broken DNS any more on modern networked *ix
> > hosts. Run a local recursive resolver and list 127.0.0.1 as the
> > first resolv.conf entry. It's 2016, guys.
>
> Why isn't a local resolver the default? Why do w
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> Why isn't a local resolver the default? Why do we rely on the ISP to
> do provide one with DHCP?
I like the way you think, sir!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-
On Mon, Aug 15, 2016 at 03:25:01AM -0700, Rick Moen wrote:
>
> There shouldn't IMO be broken DNS any more on modern networked *ix
> hosts. Run a local recursive resolver and list 127.0.0.1 as the first
> resolv.conf entry. It's 2016, guys.
Why isn't a local resolver the default? Why do we rel
25 matches
Mail list logo
