Hi, I'm struggling to find the reason why a single device (iPhone 5S) cannot resolve DNS when all other devices on the (home) LAN can.
Background
- Running UTM 9.510-5
- The pre-existing LAN has some 14 devices (NAS, Windows 10, AppleTV, iPad, iPhone (7 & 8) -- both iOS 11.4.1)
- All able to resolve DNS
- iPhone 5S is using Vodafone Pay-as-you-go with the APN set to pp.vodafone.co.uk
Issue
- Added the iPhone 5S (iOS 11.4.1) to home WiFi
- Got .39 IP
- "Usual" DNS servers 208.67.222.222 & .220.220 (as per my iPhone 7) can be seen with the DNS section of the WiFi defn. on the iPhone 5S
- Trying to connect to any web site / Apple store fails
Evidence
- Internal network: Using the iPhone 5S I can access IP addresses within the home network
- Internal network: Using the iPhone 5S I can "ping" IP addresses within the home network
- External network: Using an FQN (Example: www.google.co.uk), checking the Firewall logs I see the DNS lookup request go from the iPhone 5S's IP -> 208.67.222.222:53 stating Src MAC (iPhone) Dst MAC (.254 [the UTM]) however nothing is returned to the iPhone's browser
- External network: Using an IP address I get the same result(s) as for when I use an FQN
- External network: Using the iPhone 5S I cannot "ping" IP addresses on the internet suggesting something more "basic" is the issue
- External network: If I do the same thing (Browse, ping) from my iPhone (or a Windows Laptop etc.) the same outbound process occurs yet the web site (etc.) is displayed
Observations
- iPhone 5S has an IP + expected DNS server details yet the UTM is not relaying / not allowing the "resolved" IP (of the FQN) back to the client (the iPhone 5S in this case)
- Is there a setting "somewhere" on the iPhone which needs to be toggled as a straight "ping" from the iPhone also yields no response (i.e. a timeout)
I'm hoping someone might have hit upon this problem in the past and offer guidance as to where I should be reviewing configuration(s). As all the other 14 devices work just fine it would seem odd, though, if the UTM itself needed to be re-configured so might it be the iPhone?
Anyway, here's hoping.
Many thanks
This thread was automatically locked due to age.