Re: [Dnsmasq-discuss] Website and Dnsmasq pages

2021-02-03 Thread john doe 

On 2/3/2021 10:59 PM, - Neustradamus - wrote:

Simon, do you have my emails?

Thanks in advance.



Simon might appriciate if you could provide the redirect rules that you
suggest if you think that could  improve the web site.

The web server in question is 'Apache/2.4.38 (Debian) Server at
thekelleys.org.uk Port 443'.

--
John Doe

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Temporary failure in name resolution when IPv6 is enabled

2021-02-03 Thread Amit 
On Wed, Feb 3, 2021 at 12:16 PM Geert Stappers  wrote:
>
> On Wed, Feb 03, 2021 at 09:27:33AM -0800, Amit wrote:
> > On Tue, Feb 2, 2021 at 11:42 PM Geert Stappers  wrote:
> > > On Wed, Feb 03, 2021 at 07:36:43AM +0100, Geert Stappers wrote:
> > > > On Tue, Feb 02, 2021 at 05:57:22PM -0800, Amit wrote:
> > > > > I have been following discussions in "[Dnsmasq-discuss] v2.83 failed 
> > > > > to
> > > > > send packet: Network is unreachable" and was happy to hear it has been
> > > > > resolved in dnsmasq v2.84-1 in debian testing.
> > > > >
> > > > > However, this still seems to affect me and I get the error:
> > > > >
> > > > > $  ping www.google.com
> > > > > ping: www.google.com: Temporary failure in name resolution
> > > > >
> > > > >
> > > > > In other notes, I am able to get it to work if I disable ipv6. I have
> > > > > confirmed several users in our local environment see this issue as 
> > > > > well
> > > > > with the same setup. Let me know if there is anything else you need.
> > > >
> > > > All the links of the chain are needed.
> > >
> > > At least be aware there are multi links. Example of the chain:
> > > * root DNServer
> > > * DNServer
> > > * dnsmasq
> > > * client
> > >
> >
> > Yes, that is correct. So far there has been no change to the other
> > points in the chain. To verify a downgrade to dnsmasq 2.82 was
> > attempted and the system was able to resolve queries again.
>
> Acknowledge on "2.82" does work
> And I'm somewhat lost on "the system was able again"
>
>

I'll try to provide more details:

*Working case (ipv4):*
```
$ nmcli
wlp2s0: connected to Auto swafes
"Intel 8265 / 8275"
wifi (iwlwifi), 14:4F:8A:F0:65:2C, hw, mtu 1500
ip4 default
inet4 192.168.86.39/24
route4 0.0.0.0/0
route4 192.168.86.0/24

DNS configuration:
servers: 192.168.86.1
domains: lan
interface: wlp2s0

$ dig www.debian.org

; <<>> DiG 9.16.8-Debian <<>> www.debian.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54062
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.debian.org.INA

;; ANSWER SECTION:
www.debian.org.299INA149.20.4.15
www.debian.org.299INA128.31.0.62

;; Query time: 60 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Feb 03 13:59:07 PST 2021
;; MSG SIZE  rcvd: 75

Feb 03 13:59:07 amituttam dnsmasq[251434]: query[A] www.debian.org
from 127.0.0.1
Feb 03 13:59:07 amituttam dnsmasq[251434]: forwarded www.debian.org to
192.168.86.1
Feb 03 13:59:07 amituttam dnsmasq[251434]: reply www.debian.org is 149.20.4.15
Feb 03 13:59:07 amituttam dnsmasq[251434]: reply www.debian.org is 128.31.0.62
```

*Not working case (ipv6 "Automatic" config in Network Manager GUI):*
```
$ nmcli
wlp2s0: connected to Auto swafes
"Intel 8265 / 8275"
wifi (iwlwifi), 14:4F:8A:F0:65:2C, hw, mtu 1500
ip4 default, ip6 default
inet4 192.168.86.39/24
route4 0.0.0.0/0
route4 192.168.86.0/24
inet6 2601:647:5b00:47c:4358:3b8d:cad2:8339/64
inet6 fe80::9625:2191:bcd1:1ac6/64
route6 2601:647:5b00:47c::/64
route6 ::/0
route6 ff00::/8
route6 fe80::/64

DNS configuration:
servers: 192.168.86.1
domains: lan
interface: wlp2s0

servers: 2601:647:5b00:47c:8c90:25ff:fe1e:21c6
interface: wlp2s0

$ dig www.gnome.org

; <<>> DiG 9.16.8-Debian <<>> www.gnome.org
;; global options: +cmd
;; connection timed out; no servers could be reached

log-queries enabled (journalctl -u NetworkManager.service)
Feb 03 13:31:30 amituttam dnsmasq[251434]: query[A] www.gnome.org from 127.0.0.1
Feb 03 13:31:30 amituttam dnsmasq[251434]: forwarded www.gnome.org to
192.168.86.1
Feb 03 13:31:30 amituttam dnsmasq[251434]: forwarded www.gnome.org to
2601:647:5b00:47c:8c90:25ff:fe1e:21c6
```

Some other details in the log:

```
Feb 03 12:53:00 amituttam dnsmasq[251434]: compile time options: IPv6
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack
ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
```

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Website and Dnsmasq pages

2021-02-03 Thread - Neustradamus - 
Simon, do you have my emails?

Thanks in advance.

Regards,

Neustradamus


De : - Neustradamus - 
Envoyé : samedi 23 janvier 2021 16:07
À : dnsmasq-discuss@lists.thekelleys.org.uk
Objet : Website and Dnsmasq pages

Hello Simon,

It is possible to rename https://thekelleys.org.uk/dnsmasq/doc.html to 
https://thekelleys.org.uk/dnsmasq/index.html?
And create a redirection of doc.html to https://thekelleys.org.uk/dnsmasq/?

At the same time, to be really better, redirect http://thekelleys.org.uk/* + 
https://thekelleys.org.uk/* + http://www.thekelleys.org.uk/* to 
https://thekelleys.org.uk/*?

Currently there are 4 same "websites":
- http://www.thekelleys.org.uk/
- https://www.thekelleys.org.uk/
- http://thekelleys.org.uk/
- https://thekelleys.org.uk/

After it, it will be really better, SEO too.
- https://dropwww.com/why

Thanks in advance.

Regards,

Neustradamus

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

[Dnsmasq-discuss] CHANGELOG is not up-to-date, only 2.83

2021-02-03 Thread - Neustradamus - 
People are not sure if it is official or fake build about Dnsmasq 2.84 release 
because there is not in CHANGELOG file.
- http://www.thekelleys.org.uk/dnsmasq/CHANGELOG

Any news to have an update?

Thanks in advance.

Regards,

Neustradamus
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] v2.84 temporary failure in name resolution when IPV6 is enabled

2021-02-03 Thread Simon Kelley 
On 03/02/2021 01:57, Amit wrote:
> I have been following discussions in "[Dnsmasq-discuss] v2.83 failed to
> send packet: Network is unreachable" and was happy to hear it has been
> resolved in dnsmasq v2.84-1 in debian testing.
> 
> However, this still seems to affect me and I get the error:
> 
> $  ping www.google.com 
> ping: www.google.com : Temporary failure in name
> resolution
> 
> Which was the same error I saw in 2.83.
> 
> In other notes, I am able to get it to work if I disable ipv6. I have
> confirmed several users in our local environment see this issue as well
> with the same setup. Let me know if there is anything else you need.
> 
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 

Please could you test using "dig" rather than ping. That just does the
DNS lookup, and gives detailed information on the reply.


Also try enabling --log-queries in the dnsmasq configuration, so we can
see what's happening.


Cheers,

Simon.

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Temporary failure in name resolution when IPv6 is enabled

2021-02-03 Thread Geert Stappers 
On Wed, Feb 03, 2021 at 09:27:33AM -0800, Amit wrote:
> On Tue, Feb 2, 2021 at 11:42 PM Geert Stappers  wrote:
> > On Wed, Feb 03, 2021 at 07:36:43AM +0100, Geert Stappers wrote:
> > > On Tue, Feb 02, 2021 at 05:57:22PM -0800, Amit wrote:
> > > > I have been following discussions in "[Dnsmasq-discuss] v2.83 failed to
> > > > send packet: Network is unreachable" and was happy to hear it has been
> > > > resolved in dnsmasq v2.84-1 in debian testing.
> > > >
> > > > However, this still seems to affect me and I get the error:
> > > >
> > > > $  ping www.google.com
> > > > ping: www.google.com: Temporary failure in name resolution
> > > >
> > > >
> > > > In other notes, I am able to get it to work if I disable ipv6. I have
> > > > confirmed several users in our local environment see this issue as well
> > > > with the same setup. Let me know if there is anything else you need.
> > >
> > > All the links of the chain are needed.
> >
> > At least be aware there are multi links. Example of the chain:
> > * root DNServer
> > * DNServer
> > * dnsmasq
> > * client
> >
> 
> Yes, that is correct. So far there has been no change to the other
> points in the chain. To verify a downgrade to dnsmasq 2.82 was
> attempted and the system was able to resolve queries again.

Acknowledge on "2.82" does work
And I'm somewhat lost on "the system was able again"
 

> > Where is the `ping www.google.com` done?
> > Where and how is IPv6 disabled?
> >
> 
>  - The ping is done from a Debian linux laptop
>  - IPv6 is disabled from Network Manager by editing
> the configuration from the connection editor and disabling
> IPv6.
>  - Although disabling IPv6 is probably not the solution this was
> just an observation that disabling seems to allow queries to
> function again.


My guess:

} } Where is the `ping www.google.com` done?
} The ping is done at the end of the chain
} } Where and how is IPv6 disabled?
} Same machine,  magic from Network Manager
} 
} Although disabling IPv6 is probably not the solution this was just an
} observation that disabling seems to allow queries to function again

The dnsmasq machine has no or a broken IPv6 configuration.
Breaking IPv6 on the client at the end of the chain
results in a fallback (failback?) to IPv4.


The install of version 2.82  probably has some side effects,
side effects that cover or undo problems.

 
> If there are more details required, I can provide them.

Feedback on the guess is  appriciated.



Groeten
Geert Stappers
Subscribed to this mailinglist
-- 
Silence is hard to parse

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Temporary failure in name resolution when IPv6 is enabled

2021-02-03 Thread Amit 
On Tue, Feb 2, 2021 at 11:42 PM Geert Stappers  wrote:
>
> On Wed, Feb 03, 2021 at 07:36:43AM +0100, Geert Stappers wrote:
> > On Tue, Feb 02, 2021 at 05:57:22PM -0800, Amit wrote:
> > > I have been following discussions in "[Dnsmasq-discuss] v2.83 failed to
> > > send packet: Network is unreachable" and was happy to hear it has been
> > > resolved in dnsmasq v2.84-1 in debian testing.
> > >
> > > However, this still seems to affect me and I get the error:
> > >
> > > $  ping www.google.com
> > > ping: www.google.com: Temporary failure in name resolution
> > >
>
> Explaining why version numbers are relevant in "this problem" is also fine.
>

Updated subject. More detailed explanation:
 - The issue first appeared in v2.83 after upgrading from v2.82 for our devices.
 - An upgrade to v2.84 was forced once the fix was in debian.
 - The issue looks to still persist in the latest release as the
devices continue
to see issues in resolving DNS queries.

> > >
> > > In other notes, I am able to get it to work if I disable ipv6. I have
> > > confirmed several users in our local environment see this issue as well
> > > with the same setup. Let me know if there is anything else you need.
> >
> > All the links of the chain are needed.
>
> At least be aware there are multi links. Example of the chain:
> * root DNServer
> * DNServer
> * dnsmasq
> * client
>

Yes, that is correct. So far there has been no change to the other
points in the chain. To verify a downgrade to dnsmasq 2.82 was
attempted and the system was able to resolve queries again.

> Where is the `ping www.google.com` done?
> Where and how is IPv6 disabled?
>

 - The ping is done from a Debian linux laptop
 - IPv6 is disabled from Network Manager by editing
the configuration from the connection editor and disabling
IPv6.
 - Although disabling IPv6 is probably not the solution this was
just an observation that disabling seems to allow queries to
function again.

If there are more details required, I can provide them.

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss