Skip to content

Add missing dnsmasq setup instructions for macOS #11437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nbudin merged 1 commit into from
May 8, 2026
+20 −2
Merged

Add missing dnsmasq setup instructions for macOS #11437

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 20 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,6 +187,24 @@ domain intercode.test
nameserver 127.0.0.1
```

This tells macOS that for intercode.test and all its subdomains, it should use the DNS server running on your local machine to resolve them. Next, we'll need to put a DNS server on your local machine. Run this to install dnsmasq:

```text
brew install dnsmasq
```

Edit the file at /opt/homebrew/etc/dnsmasq.conf and add the following content:

```text
address=/intercode.test/127.0.0.1
```

Finally, run this to get dnsmasq started and configure it to automatically start whenever your computer starts:

```text
sudo brew services start dnsmasq
```

To test that this is working, try running `ping randomname.intercode.test`. It should start pinging your local machine on 127.0.0.1.

</details>
Expand All @@ -195,7 +213,7 @@ To test that this is working, try running `ping randomname.intercode.test`. It s

<summary>Linux</summary>

On Linux, there's no built-in way to do wildcard domain resolution like there is with macOS's resolver. But, we can use dnsmasq as a DNS resolver proxy and configure it to resolve \*.intercode.test to 127.0.0.1. First, install dnsmasq:
On Linux, there's no built-in way to do host-specific DNS resolution like there is with macOS's resolver. But, we can use dnsmasq as a DNS resolver proxy and configure it to resolve \*.intercode.test to 127.0.0.1. First, install dnsmasq:

```sh
sudo apt install dnsmasq
Expand Down Expand Up @@ -245,7 +263,7 @@ To test that this is working, try running `ping randomname.intercode.test`. It s
<details>
<summary>Windows</summary>

On Windows, there's no built-in way to do wildcard domain resolution like there is with macOS's resolver. But, we can use a DNS resolver proxy such as [Acrylic](https://mayakron.altervista.org/support/acrylic/Home.htm) and configure it to resolve \*.intercode.test to 127.0.0.1.
On Windows, there's no built-in way to do host-specific DNS resolution like there is with macOS's resolver. But, we can use a DNS resolver proxy such as [Acrylic](https://mayakron.altervista.org/support/acrylic/Home.htm) and configure it to resolve \*.intercode.test to 127.0.0.1.

I have not personally tried this, but if someone does and would like to contribute instructions to this README, I would be forever grateful!

Expand Down
Loading