MetaMask / MetaMask/metamask-extension

Advanced setting to disable the built-in ENS resolver

Open
#7,042 0 comments 0 reactions 0 assignees View on GitHub
area-devmode type-enhancement
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**What problem are you trying to solve?**
When testing my own ENS resolver - the metamask chome extension always seems to get precedence in resolving ENS names, so I always have to disable Metamask completely before it queries my own DNS resolver. Could disabling the ENS resolver become an item in the advanced settings ?

**Describe the solution you'd like**
A setting to enable/disable the ENS resolver completely in the advanced settings.

Contributor guide

Open the contributing guide

Research direction

The issue provides no file or test path. Start by locating the ENS resolver integration and the advanced-settings entry point, then trace how ENS lookups are selected. Done means users can disable the built-in ENS resolver from advanced settings so their own resolver is queried instead.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.