How to fix MetaMask not displaying ENS domain as my wallet name?

ENS Resolution Configuration

1. Ensure your MetaMask wallet address is properly registered with an ENS domain through the official ENS app at app.ens.domains. Registration requires sending a transaction to claim the domain and setting the resolver.

2. Confirm that the ENS domain has a valid resolver configured. Without a resolver, no reverse or forward resolution can occur. Check this in the ENS app under the “Resolver” tab for your domain.

3. Verify that the resolver has been assigned correctly — it must be set to the default public resolver (0x4976fb03C32e5B8cfe2b6cCB31c09Ba78EBaBa41) unless you're using a custom one with full compatibility.

4. Make sure the domain’s owner address matches the MetaMask account you’re using. If ownership was transferred or delegated, the new controller must explicitly set the reverse record.

Reverse Record Setup

1. Reverse resolution maps your wallet address back to its ENS name. Without it, MetaMask cannot display the domain as your wallet label.

2. In the ENS app, navigate to your domain, click “Set Reverse Record”, and select the connected MetaMask account as the target.

3. Submit the transaction and wait for confirmation on-chain. This step is mandatory even if forward resolution is already active.

4. After confirmation, refresh MetaMask by toggling the network or restarting the browser extension. The wallet name should update within seconds if all records are live.

Browser and Extension Sync Issues

1. Clear MetaMask’s local cache by going to Settings → Advanced → Reset Account. This forces a fresh fetch of ENS metadata from the blockchain.

2. Disable any browser extensions that may interfere with web3 injection, such as ad blockers or privacy tools that filter DNS requests to ENS subdomains.

3. Confirm that your browser is not using a custom DNS provider like Cloudflare 1.1.1.1 or Google DNS that blocks or delays .eth resolution queries — some resolvers rely on specific DNS endpoints.

4. Try switching MetaMask’s network to Ethereum Mainnet temporarily, then back to your target chain. This triggers a reinitialization of ENS lookups across all supported networks.

Smart Contract Verification Conflicts

1. If your ENS domain points to a contract address instead of an externally owned account (EOA), MetaMask will not resolve it as a wallet name unless the contract implements the required EIP-1559-compatible interface for reverse resolution.

2. Check whether the address associated with the domain is verified on Etherscan as an EOA. Contracts without proper EIP-2052 support will fail silent resolution attempts.

3. Avoid using wrapped or proxy contracts for primary wallet identification. These often lack the necessary fallback functions needed for seamless ENS integration.

4. If you recently changed the address linked to your domain, allow at least two block confirmations before expecting MetaMask to reflect the change — caching layers may retain stale values.

Frequently Asked Questions

Q: Why does my ENS domain show up in Etherscan but not in MetaMask?MetaMask relies on reverse record configuration, not just forward resolution. Even if your domain resolves to an address on Etherscan, MetaMask needs the reverse mapping to display it as a wallet name.

Q: Can I use an ENS subdomain like wallet.myname.eth in MetaMask?Yes, provided the subdomain has its own resolver configured and a reverse record set to your wallet address. Subdomains require independent setup — inheritance from parent domains does not apply automatically.

Q: Does MetaMask support ENS names on testnets like Sepolia or Polygon?Only if the testnet has deployed a compatible ENS registry and resolver. Sepolia supports ENS natively; Polygon requires manual RPC configuration and third-party resolver deployment, which many users overlook.

Q: What happens if I change my wallet address after setting the reverse record?The old reverse record remains active until manually updated or overwritten. MetaMask continues displaying the prior ENS name until a new transaction sets the reverse record for the new address.