Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle T-Mobile and Deutsche Telekom cases properly #688

Closed
ameshkov opened this issue Mar 6, 2018 · 1 comment
Closed

Handle T-Mobile and Deutsche Telekom cases properly #688

ameshkov opened this issue Mar 6, 2018 · 1 comment

Comments

@ameshkov
Copy link
Member

ameshkov commented Mar 6, 2018

T-Mobile relies on their own custom DNS server in order to provide connectivity with IPv4 servers over their IPv6-only network.

Domain names are resolved to some private IPv6 addresses which are then re-routed to the real IPv4 addresses (invisibly for the user).

The problem with that is that you simply cannot use a custom DNS server in that case. At least we need to warn T-Mobile users about that.

We need help from T-Mobile users who have this issue

@ameshkov ameshkov added this to the 2.1.0 milestone Mar 6, 2018
@ameshkov ameshkov changed the title Handle T-Mobile case properly Handle T-Mobile and Deutsche Telekom case properly Mar 6, 2018
@ameshkov ameshkov changed the title Handle T-Mobile and Deutsche Telekom case properly Handle T-Mobile and Deutsche Telekom cases properly Mar 6, 2018
@dnovitskyi
Copy link

dnovitskyi commented Mar 14, 2018

We've got something that looks like the same but is related to Japanese carrier DOCOMO.
Logs and all related information available under 543636.
Here, however, the problems only occur when using LTE networks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants