On Fri, Sep 18, 2020 at 2:59 PM Geert Stappers wrote:
>
> On Fri, Sep 18, 2020 at 08:08:07AM +0800, Hongyi Zhao wrote:
> > On Thu, Sep 17, 2020 at 07:25:43AM +0800, Hongyi Zhao wrote:
> > >
> > > But I still can't figure out what's the wrong configuration or
> > > **bug** (may or may not exist,
On Fri, Sep 18, 2020 at 08:08:07AM +0800, Hongyi Zhao wrote:
> On Thu, Sep 17, 2020 at 07:25:43AM +0800, Hongyi Zhao wrote:
> >
> > But I still can't figure out what's the wrong configuration or
> > **bug** (may or may not exist, I'm not sure.) in dnsmasq itself
> > triggered this problem.
>
> I
On Thu, Sep 17, 2020 at 2:04 PM Geert Stappers wrote:
>
> On Thu, Sep 17, 2020 at 07:25:43AM +0800, Hongyi Zhao wrote:
> >
> > But I still can't figure out what's the wrong configuration or
> > **bug** (may or may not exist, I'm not sure.) in dnsmasq itself
> > triggered this problem.
I can
On Wed, Sep 16, 2020 at 04:16:40PM +0800, Hongyi Zhao wrote:
> On Wed, Sep 16, 2020 at 3:06 PM Dominick C. Pastore wrote:
> > On Wed, Sep 16, 2020, at 1:36 AM, Geert Stappers wrote:
> > > > > I was a little surprised this one worked since the previous one
> > > > > didn't, but I suspect
On Thu, Sep 17, 2020 at 07:25:43AM +0800, Hongyi Zhao wrote:
>
> But I still can't figure out what's the wrong configuration or
> **bug** (may or may not exist, I'm not sure.) in dnsmasq itself
> triggered this problem.
Acknowledge
___
On Thu, Sep 17, 2020 at 7:02 AM Hongyi Zhao wrote:
>
> Further testing again:
>
> Even I don't use the dnsasmq resolver in systemd, the problem still
> will appear. See following for more info:
>
> $ resolvectl status | grep 'DNS Server'
> Current DNS Server: 114.114.114.114
> DNS
On Thu, Sep 17, 2020 at 6:28 AM Hongyi Zhao wrote:
>
> On Wed, Sep 16, 2020 at 9:31 PM Hongyi Zhao wrote:
> >
> > On Tue, Sep 15, 2020 at 9:47 PM Hongyi Zhao wrote:
> > >
> > > On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
> > > wrote:
> > > >
> > > > On Mon, Sep 14, 2020, at 8:03 PM,
On Wed, Sep 16, 2020 at 9:31 PM Hongyi Zhao wrote:
>
> On Tue, Sep 15, 2020 at 9:47 PM Hongyi Zhao wrote:
> >
> > On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
> > wrote:
> > >
> > > On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > > > I run dnsmasq as following:
> > > >
> > > >
On Tue, Sep 15, 2020 at 9:47 PM Hongyi Zhao wrote:
>
> On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
> wrote:
> >
> > On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > > I run dnsmasq as following:
> > >
> > > $ /usr/local/sbin/dnsmasq --port=53 -c10240 --server=127.0.0.1#6053
> >
On Wed, Sep 16, 2020 at 2:03 PM Geert Stappers wrote:
>
> On Wed, Sep 16, 2020 at 01:19:27PM +0800, Hongyi Zhao wrote:
> > On Wed, Sep 16, 2020 at 11:18 AM Dominick C. Pastore wrote:
> ...
> > >
> > > This does indeed seem strange. Unfortunately, I'm not sure either. The
> > > best I can
On Wed, Sep 16, 2020 at 3:06 PM Dominick C. Pastore
wrote:
>
> On Wed, Sep 16, 2020, at 1:36 AM, Geert Stappers wrote:
> > > > I was a little surprised this one worked since the previous one
> > > > didn't, but I suspect systemd-resolved is falling back to the
> > > > FallbackDNS servers (which
On Wed, Sep 16, 2020 at 2:03 PM Geert Stappers wrote:
>
> On Wed, Sep 16, 2020 at 01:19:27PM +0800, Hongyi Zhao wrote:
> > On Wed, Sep 16, 2020 at 11:18 AM Dominick C. Pastore wrote:
> ...
> > >
> > > This does indeed seem strange. Unfortunately, I'm not sure either. The
> > > best I can
On Wed, Sep 16, 2020, at 1:36 AM, Geert Stappers wrote:
> > > I was a little surprised this one worked since the previous one
> > > didn't, but I suspect systemd-resolved is falling back to the
> > > FallbackDNS servers (which are hardcoded in if not set explicitly).
>
> > What's the FallbackDNS
On Wed, Sep 16, 2020 at 01:19:27PM +0800, Hongyi Zhao wrote:
> On Wed, Sep 16, 2020 at 11:18 AM Dominick C. Pastore wrote:
...
> >
> > This does indeed seem strange. Unfortunately, I'm not sure either. The
> > best I can suggest is to check the syslog for any clues, if you
> > haven't yet.
>
On Wed, Sep 16, 2020 at 11:18 AM Dominick C. Pastore
wrote:
>
> On Tue, Sep 15, 2020, at 9:47 AM, Hongyi Zhao wrote:
> > On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
> > wrote:
> > >
> > > On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > > > I run dnsmasq as following:
> > > >
>
On Tue, Sep 15, 2020, at 9:47 AM, Hongyi Zhao wrote:
> On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
> wrote:
> >
> > On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > > I run dnsmasq as following:
> > >
> > > $ /usr/local/sbin/dnsmasq --port=53 -c10240 --server=127.0.0.1#6053
> > >
On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
wrote:
>
> On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > I run dnsmasq as following:
> >
> > $ /usr/local/sbin/dnsmasq --port=53 -c10240 --server=127.0.0.1#6053
> >
On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
wrote:
>
> On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > I run dnsmasq as following:
> >
> > $ /usr/local/sbin/dnsmasq --port=53 -c10240 --server=127.0.0.1#6053
> >
On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> I run dnsmasq as following:
>
> $ /usr/local/sbin/dnsmasq --port=53 -c10240 --server=127.0.0.1#6053
> --conf-dir=/home/werner/Public/anti-gfw/dns/dnsmasq/conf/conf-dir,*.conf
> -C /home/werner/Public/anti-gfw/dns/dnsmasq/conf/dnsmasq.conf
>
On Mon, Sep 14, 2020 at 10:45 PM Dominick C. Pastore
wrote:
>
> > > Personally, I am not a fan of Netplan for reasons like this. It's
> > > supposed to abstract away the details of NetworkManager or
> > > systemd-networkd, but it doesn't do a great job of it. You end up having
> > > to refer
> > Personally, I am not a fan of Netplan for reasons like this. It's supposed
> > to abstract away the details of NetworkManager or systemd-networkd, but it
> > doesn't do a great job of it. You end up having to refer to the
> > NetworkManager or systemd-networkd documentation anyway, and
On Mon, Sep 14, 2020 at 12:31 PM Dominick C. Pastore
wrote:
>
> On Sun, Sep 13, 2020, at 10:44 PM, Hongyi Zhao wrote:
> > On Mon, Sep 14, 2020 at 9:02 AM Neal P. Murphy
> > wrote:
> > >
> > > On Mon, 14 Sep 2020 06:52:49 +0800
> > > Hongyi Zhao wrote:
> > >
> > > > On Mon, Sep 14, 2020 at 4:26
On Sun, Sep 13, 2020, at 10:44 PM, Hongyi Zhao wrote:
> On Mon, Sep 14, 2020 at 9:02 AM Neal P. Murphy
> wrote:
> >
> > On Mon, 14 Sep 2020 06:52:49 +0800
> > Hongyi Zhao wrote:
> >
> > > On Mon, Sep 14, 2020 at 4:26 AM Geert Stappers
> > > wrote:
> > > >
> > > > On Sun, Sep 13, 2020 at
On Mon, Sep 14, 2020 at 9:02 AM Neal P. Murphy
wrote:
>
> On Mon, 14 Sep 2020 06:52:49 +0800
> Hongyi Zhao wrote:
>
> > On Mon, Sep 14, 2020 at 4:26 AM Geert Stappers wrote:
> > >
> > > On Sun, Sep 13, 2020 at 03:36:42PM +0800, Hongyi Zhao wrote:
> > > > So I want to know how to solve the
On Mon, 14 Sep 2020 06:52:49 +0800
Hongyi Zhao wrote:
> On Mon, Sep 14, 2020 at 4:26 AM Geert Stappers wrote:
> >
> > On Sun, Sep 13, 2020 at 03:36:42PM +0800, Hongyi Zhao wrote:
> > > So I want to know how to solve the confliction problem between dnsmasq
> > > and systemd-resolved.
> >
> >
On Mon, Sep 14, 2020 at 4:26 AM Geert Stappers wrote:
>
> On Sun, Sep 13, 2020 at 03:36:42PM +0800, Hongyi Zhao wrote:
> > Hi,
> >
> > On Ubuntu 20.04, I let dnsmasq listen on 127.0.0.1:53, at the same
> > time, I also noted that systemd-resolved has a default stub dns
> > resolver which is
On Sun, Sep 13, 2020 at 03:36:42PM +0800, Hongyi Zhao wrote:
> Hi,
>
> On Ubuntu 20.04, I let dnsmasq listen on 127.0.0.1:53, at the same
> time, I also noted that systemd-resolved has a default stub dns
> resolver which is listening on 127.0.0.53:53.
>
> And for my case, the /etc/resolv.conf is
Hi,
On Ubuntu 20.04, I let dnsmasq listen on 127.0.0.1:53, at the same
time, I also noted that systemd-resolved has a default stub dns
resolver which is listening on 127.0.0.53:53.
And for my case, the /etc/resolv.conf is a symlink as following:
$ realpath -e /etc/resolv.conf
28 matches
Mail list logo