I thought it was a pretty standard DNS client implementation to move past
unresponsive DNS servers.
We hand out several internal DNS servers to our corporate endpoints and I
really hope they will quickly try the next DNS server if one server happens to
be down for whatever reason.
Windows
s/MUST no/MUST not/g
On Sun, Apr 24, 2016 at 8:49 PM, Brzozowski, John Jason
wrote:
> Operators MUST no advertise DNS server IPv6 addresses if they do not
> work. The fix is simple. I would like to see as much happening over IPv6
> as possible, the last thing I really want to see is more happy
Operators MUST no advertise DNS server IPv6 addresses if they do not work.
The fix is simple. I would like to see as much happening over IPv6 as
possible, the last thing I really want to see is more happy (happier) eye
ball implementations.
On Sun, Apr 24, 2016 at 8:35 PM, Lorenzo Colitti wrote:
Ted,
> On Apr 24, 2016, at 3:55 PM, Ted Mittelstaedt wrote:
> Now I will also point out something else that affects ISPs - like
> Comcast (are you listening?) - and probably affected "this Belgian ISP"
> that Erik is reporting.
>
> The issue really isn't what protocol is supported. The issue i
Ted,
On 25/04/2016 07:55, Ted Mittelstaedt wrote:
> Why Android doesn't support DHCPv6 is detailed here:
>
> https://code.google.com/p/android/issues/detail?id=32621#c53
Yes, we all know Lorenzo's opinion, and the follow-up comments there
give the opposing opinions.
>
> They say to use SLAAC an
Why Android doesn't support DHCPv6 is detailed here:
https://code.google.com/p/android/issues/detail?id=32621#c53
They say to use SLAAC and RFC6106. I happen agree with their reasoning.
It is Microsoft who needs to change, not Google. The IPv6 standard
does not require DHCPv6 and it's a mod
"Brzozowski, John Jason" writes:
> As long as we have either DHCPv6 or RFC6106
Shouldn't that be "as long as we have DHCPv6 and RFC6106"? Android does
not support DHCPv6 and (AFAIK) Microsoft does not support RFC6106. So in
a mixed environment you need both.
Jens, who just opened a case at Ci
As long as we have either DHCPv6 or RFC6106 we can make this work to enable
IPv6 only for devices like phones, etc. Between DHCPv6 and RFC6106 we have
most devices covered. A co-worker recently introduced me to the Linux
package for RDNSS.
On Sun, Apr 24, 2016 at 11:37 AM, Matthew Huff wrote:
On Sun, 24 Apr 2016, Matthew Huff wrote:
Remember, Android developers refuse to implement DHCPv6 and so can only
get DNS server info from RDDNS (rfc6106). Since the number RA devices
that support RFC6106 are limited, this provides another problem set for
Android devices and IPv6
Well, this
Remember, Android developers refuse to implement DHCPv6 and so can only get
DNS server info from RDDNS (rfc6106). Since the number RA devices that
support RFC6106 are limited, this provides another problem set for Android
devices and IPv6
Matthew Huff | 1 Manhattanville
Has someone done testing to very that the same issue doesn't affect,
say, Lollipop?
On 24 April 2016 at 23:17, Eric Vyncke (evyncke) wrote:
> Jeroen, Erik and John,
>
> Thanks for the hint. I will advise the ISP to investigate any DNS issue
> (such as not returning an error message when requestin
Android is properly trying to query DNS over IPv6 unlike other
devices/OSes. Most other mobile platforms still prefer the querying of DNS
over IPv4 for A/ RR query types.
On Sun, Apr 24, 2016 at 10:17 AM, Eric Vyncke (evyncke)
wrote:
> Jeroen, Erik and John,
>
> Thanks for the hint. I will
On 2016-04-24 16:17, Eric Vyncke (evyncke) wrote:
> Jeroen, Erik and John,
>
> Thanks for the hint. I will advise the ISP to investigate any DNS issue
> (such as not returning an error message when requesting a non-existing
> ) but I wonder why it is linked to that specific Android Marshmallow
Jeroen, Erik and John,
Thanks for the hint. I will advise the ISP to investigate any DNS issue (such
as not returning an error message when requesting a non-existing ) but I
wonder why it is linked to that specific Android Marshmallow version.
-éric
From:
mailto:ipv6-ops-bounces+evyncke=c
My customers saw this issue at one point. We had issues with DNS over
IPv6. Bad DNS and/or network configurations. Once these were fixed, the
problems cleared up.
On Sunday, April 24, 2016, Erik Kline wrote:
> On 24 April 2016 at 19:53, Jeroen Massar >
> wrote:
> > On 2016-04-24 11:51, Eric V
On 2016-04-24 11:51, Eric Vyncke (evyncke) wrote:
> One of the first Belgian ISP to deploy IPv6 (VOO) is now recommending to
> its Android Marshmallow (6.0.1) users to deactivate IPv6 on their
> residential WiFi CPE... :-(
>
> It appears that the issue is about IPv6 web sites/apps being really
> s
One of the first Belgian ISP to deploy IPv6 (VOO) is now recommending to its
Android Marshmallow (6.0.1) users to deactivate IPv6 on their residential WiFi
CPE... :-(
It appears that the issue is about IPv6 web sites/apps being really slower when
using IPv6.
AFAIK, it is only related to this s
17 matches
Mail list logo