Android app fails to follow Round Robin DNS

### ⚠️ Before posting ⚠️

- [X] This is a **bug**, not a question or an enhancement.
- [X] I've [searched for similar issues](https://github.com/nextcloud/android/issues) and didn't find a duplicate.
- [X] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).

### Steps to reproduce

Have a dns record with a round robin, with some ips within it not pointing to nextcloud
Attempt to add the server to the app
Notice how it errors out with host not found despite there being a Nextcloud instance on that domain

### Expected behaviour

The app works normally and allows usage of the instance

### Actual behaviour

The app fails with host not found

### Android version

13

### Device brand and model

Pixel 7 pro

### Stock or custom OS?

Custom (explain in "additional information")

### Nextcloud android app version

3.26.0

### Nextcloud server version

27.1.3

### Using a reverse proxy?

Yes

### Android logs

Apologies my phone is not with me, the log will be uploaded in the morning
Edit: tried Nextcloud dev but I couldn’t find the log file after, it still fails

### Server error logs

```bash
Not relevant
```

### Additional information

Device is rooted but runs stock pixel os

My dns records are as follows
```
Nextcloud.internal CNAME kuberound.internal
kuberound.internal A (node 1 ip)
kuberound.internal A (node 2 ip)
kuberound.internal A (node 3 ip)
~~redacted for brevity, there are 2 more nodes~~
```
When giving Nextcloud.internal it’s own A record pointing straight to one node it does work properly, when giving Nextcloud.internal it’s own round robin it errors out
This is possibly a regression as I tried version 3.22.2 and it worked as expected