[Bug]: ENS subdomain resolution not working

**Describe the bug**
When I introduce an ENS subdomain, the address don't resolve.

**Screenshots**
See Mobile (left) not resolving, whereas the same subdomain resolving on Extension (right) on Mainnet.

https://user-images.githubusercontent.com/54408225/214580225-5b0e283d-d013-42ff-bd57-c1d10fe696e1.mp4

**To Reproduce**
_Steps to reproduce the behavior_
1. Select Mainnet
2. Click on Send
3. Add this recipient `1.offchainexample.eth`
4. Wait -- ENS subdomain never resolves

**Expected behavior**
ENS subdomain should resolve to the correct address (like in Extension).

**Smartphone (please complete the following information):**

- Device: Samsung SM-A217F
- OS: Android 11.0
- App Version: v5.12.3 (1033)

-------------------------------------------------------------
_to be added after bug submission by internal support / PM_
**Severity**

- How critical is the impact of this bug on a user?
- Add stats if available on % of customers impacted
- Is this visible to all users?
- Is this tech debt?

No file or test is named. Start by reproducing the Mainnet send flow on Android with recipient 1.offchainexample.eth and compare it with the Extension behavior. Done means the ENS subdomain resolves to the correct address in the mobile app.

Written by the indexing model from the issue text.