DNS Problems with Mobile Data

[moxx]

Same for me, downgrading helped, thank you very much! As I use the phone as daily driver, this quick fix was very important for me.

With this line I also prevent apt from updating libnm0:

Code:

echo -en 'Package: libnm0\nPin: version 1.35.*\nPin-Priority: -1\n\n' >> /etc/apt/preferences

[powo01]

In my case after the update there was the mobile ipv6 address and dns missing. Both was send by the mobile provider and I saw it
in the modem manager log. But at adding the ipv6 a fault was shown. After the rollback to the version before anything working again.

[arno_nuehm]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

[Zdenek]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

Hi, I've done "apt upgrade" right now and the mobile data is working again.
Before that I didn't change anything in configuration scripts, so for me the new version of Network Manager works correctly now...
Also dbus packages were upgraded but I'm not sure if that could have any effect...

[user641]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

for me the v1.36.0-2 solved the problem, I did nothing else than upgrading, and it's working the whole time now

[arno_nuehm]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

for me the v1.36.0-2 solved the problem, I did nothing else than upgrading, and it's working the whole time now

Thanks for mentioning!

Since I used the workaround via installing resolvconf and adding a new DNS server, I first removed the package resolvconf and then updated network-manager. But it seems, this removed another config file and the DNS server of the mobile provider is still not forwarded into /etc/resolv.conf.

After re-installing resolvconf without manually adding a DNS server, everything works fine after rebooting.

[grump_fiddle_reinstall]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

for me the v1.36.0-2 solved the problem, I did nothing else than upgrading, and it's working the whole time now

Thanks for mentioning!

Since I used the workaround via installing resolvconf and adding a new DNS server, I first removed the package resolvconf and then updated network-manager. But it seems, this removed another config file and the DNS server of the mobile provider is still not forwarded into /etc/resolv.conf.

After re-installing resolvconf without manually adding a DNS server, everything works fine after rebooting.

All working again here after this morning's updates. I decided not to try the workaround so didn't need to fix anything else.

[user641]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

for me the v1.36.0-2 solved the problem, I did nothing else than upgrading, and it's working the whole time now

Thanks for mentioning!

Since I used the workaround via installing resolvconf and adding a new DNS server, I first removed the package resolvconf and then updated network-manager. But it seems, this removed another config file and the DNS server of the mobile provider is still not forwarded into /etc/resolv.conf.

After re-installing resolvconf without manually adding a DNS server, everything works fine after rebooting.

All working again here after this morning's updates. I decided not to try the workaround so didn't need to fix anything else.

Just receive an update of modemmanager too, if I remember correctly the previous version had a bug that used to make me change the APN every now and then.

[TRS-80]

All working again here after this morning's updates. I decided not to try the workaround so didn't need to fix anything else.

Thanks for report! I had been holding off on updating after reading this issue, but now I feel more confident to go ahead.

[Fish]

Sadly, the latest Network Manager update to v1.36.0-2 hasn't solved the problem. DNS resolving is still broken and a manual DNS server adress is still needed.

Same here... Reinstalling resolvconf didn´t help either.