Hi, I have a problem with Seafile Pro app on iPhone. I have a split DNS setup for LAN devices. Otherwise they can’t connect. And Seafile fails to connect. While it works properly on mobile internet, I assume because it is an outside network.
I have other services on the same server that work with their iPhone apps. So this makes me think that Seafile is doing something strange instead of using the network as usual.
Or is there anything else that could be wrong?
I assume iOS client may still try to connect using public IP address regardless of split DNS setup due to cache. Have you considered configuring Hairpin NAT?
What kind of cache do you mean? I’m pretty sure the iphone has not seen this dns name ever before, it has stayed within the LAN before I tried to login. The dns TTL is a couple of minutes. And there is no other device on the LAN with such an issue.
This Hairpin NAT sounds to be what is generally known as NAT loopback for the forwarded ports. In OpenWRT that can be done with “Enable NAT Loopback” in advanced firewall settings where ports are forwarded.
Basically this has to work. The point is not to have internal traffic needlessly processed by the router. So I have disabled that to make sure devices don’t accidentally load the router CPU unnecessarily while communicating in the internal network which is much faster than the external.
But this brings me back to the original question - what DNS is seafile app using instead of the LAN provided one and why? Also how to disable that unwanted DNS?