[Fixed in 1.0.7.16] Sailfish and Android apps using different DNS? [released]

answered 2014-01-07 13:48:07 +0200

vandersmash
443 ●4 ●13 ●15

updated 2014-01-07 18:15:17 +0200

Nux
8262 ●77 ●91 ●96

http://enux.eu/

Please allow my to add to the suggested answer:

1st I have blocked Alien Dalviks access to the Google DNS by adding entries to IP tables of Sailfish host OS:

iptables -A INPUT -s 8.8.8.8 -j DROP
iptables -A INPUT -s 8.8.4.4 -j DROP
iptables -A OUTPUT -d 8.8.8.8 -j DROP
iptables -A OUTPUT -d 8.8.4.4 -j DROP

Screen: http://sdrv.ms/1cVC0oP

After this your'll notice some applications like Yandex or Storypod don't work anymore. That means mission succces, no more Google DNS connectivity allowed.

How to get back DNS functionality?

2nd Set DNS to your choice (example with OpenDNS)

Edit /opt/alien/system/build.prop and add:

net.rmnet0.dns1=208.67.222.222
net.rmnet0.dns2=208.67.220.220
net.dns1=208.67.222.222
net.dns2=208.67.220.220

3rd create the file /opt/alien/system/etc/resolve.conf and include following (again replace the ip address with the DNS server of your choice from step 2)

nameserver 208.67.222.222
nameserver 208.67.220.220

Restart Alien Dalvik (reboot the Jolla) and test.

Note:

• Tested the Jolla with blocked Google DNS servers blocked on the router. All is fine now.
• Google DNS seems very hard coded, primary DNS stays on 8.8.8.8 and the new DNS is used only as a secondary DNS. (Myriad must be really in bed with Google to program such hardcore virus style behavior - or is it Jolla that has pre-configured the Alien Dalvik package options?)
• Result is that address resolving takes a little longer.
• Not sure if step 2 is required. As somebody has mentioned, as a stand alone solution it does not work.

Looking forward to read about somebody finding out how to erase 8.8.8.8 as primary DNS permanently.

answered 2014-04-11 23:09:00 +0200

dazo
2241 ●37 ●49 ●46

I've approached this differently. I used iptables NAT rules to forward all DNS requests towards 8.8.8.8 and 8.8.4.4 to be processed by 127.0.0.1 instead. That have worked flawlessly for me.

I set up firewalling like I described here: https://together.jolla.com/question/11075/how-to-setup-firewall-iptables-init-scripts/#37141 Then I added these iptables rules:

iptables -t nat -A OUTPUT -d 8.8.8.8/32 -p udp -m udp --dport 53 -j DNAT --to-destination 127.0.0.1:53
iptables -t nat -A OUTPUT -d 8.8.8.8/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 127.0.0.1:53
iptables -t nat -A OUTPUT -d 8.8.4.4/32 -p udp -m udp --dport 53 -j DNAT --to-destination 127.0.0.1:53
iptables -t nat -A OUTPUT -d 8.8.4.4/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 127.0.0.1:53

With my little systemd-iptables wrapper setup, I saved these rules and ensured the iptables unit was being started at boot using these lines:

 [root@Jolla ~]# /usr/local/sbin/systemd-iptables save
 [root@Jolla ~]# systemctl enable iptables.service
 [root@Jolla ~]# systemctl start iptables.service

answered 2014-01-05 07:49:46 +0200

Nux
8262 ●77 ●91 ●96

http://enux.eu/

Haven't check that, but I think you should be able to change DNS by adding below to /opt/alien/system/build.prop. Note that you need to modify it as root.

# Google DNS Tweak
net.rmnet0.dns1=1.2.3.4
net.rmnet0.dns2=5.6.7.8
net.dns1=1.2.3.4
net.dns2=5.6.7.8

Based on: http://forum.xda-developers.com/showthread.php?t=1706154

answered 2014-04-28 19:20:45 +0200

wickedsp1d3r
533 ●14 ●23 ●25

updated 2014-04-28 20:06:37 +0200

chattr +i /etc/resolv.conf is working. Resolv.conf does not reset on reboot after that command.