Revision history [back]
 | 1 | initial version | posted 2013-12-26 17:59:46 +0300  |
Sailfish and Android apps using different DNS?
It seems that Android applications do not use the same DNS resolver as native Sailfish applications. I noticed this because I have my home network set up to use a local DNS server, and Sailfish catches this correctly, while Android applications do not.
The result is that I can access my local machines using their fully qualified domain names (e.g. wok.oblomov.eu) from e.g. the Sailfish browser, but not from e.g. Opera for Android.
Sailfish and Android apps using different DNS?
It seems that Android applications do not use the same DNS resolver as native Sailfish applications. I noticed this because I have my home network set up to use a local DNS server, and Sailfish catches this correctly, while Android applications do not.
The result is that I can access my local machines using their fully qualified domain names (e.g. wok.oblomov.eu) from e.g. the Sailfish browser, but not from e.g. Opera for Android.
| | 3 | No.3 Revision |
Sailfish and Android apps using different DNS?
It seems that Android applications do not use the same DNS resolver as native Sailfish applications. I noticed this because I have my home network set up to use a local DNS server, and Sailfish catches this correctly, while Android applications do not.
The result is that I can access my local machines using their fully qualified domain names (e.g. wok.oblomov.eu) from e.g. the Sailfish browser, but not from e.g. Opera for Android.
EDIT: after installing a terminal emulator for Android I can confirm that getprop net.dns1 returns 8.8.8.8 instead of 127.0.0.1, which is what is found in /etc/resolv.conf, so Android _is_ using a different DNS than Sailfish OS. This should be changed.
| | 4 | No.4 Revision |
[Fixed in 1.0.7.16] Sailfish and Android apps using different DNS?
It seems that Android applications do not use the same DNS resolver as native Sailfish applications. I noticed this because I have my home network set up to use a local DNS server, and Sailfish catches this correctly, while Android applications do not.
The result is that I can access my local machines using their fully qualified domain names (e.g. wok.oblomov.eu) from e.g. the Sailfish browser, but not from e.g. Opera for Android.
EDIT: after installing a terminal emulator for Android I can confirm that getprop net.dns1 returns 8.8.8.8 instead of 127.0.0.1, which is what is found in /etc/resolv.conf, so Android _is_ using a different DNS than Sailfish OS. This should be changed.
Update: Closed this question, as it is on the list of bugs fixed in 1.0.7.16 Saapunki.