Skip to content

feat: forward guest DNS to Docker's embedded resolver#793

Open
alimx07 wants to merge 2 commits into
urunc-dev:mainfrom
alimx07:feat/add-docker-dns
Open

feat: forward guest DNS to Docker's embedded resolver#793
alimx07 wants to merge 2 commits into
urunc-dev:mainfrom
alimx07:feat/add-docker-dns

Conversation

@alimx07

@alimx07 alimx07 commented Jun 28, 2026

Copy link
Copy Markdown

Description

On Docker user custom networks the DNS resolver (127.0.0.11) is loopback only and unreachable by the unikernel guest. Detect this case per container, expose the resolver via a virtual resolver IP (Last Subnet IP) using tc redirects between the tap and lo + a PREROUTING DNAT (for DNS server ports), and rewrite the guest's resolv.conf to point at that IP in our unikernel is linux one.

Two TC rules added on tap and lo:

  • Tap : Redirect packets to resolvIP into lo
  • Lo : Redirect packets with src=ResolvIP into Tap

Related issues

How was this tested?

Tested in user custom docker network with urunc container u1 and normal one u2:

u1 lookup on github.com

/ # nslookup github.com
Server:		172.24.255.254
Address:	172.24.255.254:53

Non-authoritative answer:
Name:	github.com
Address: 140.82.121.3

u1 lookup on u2

/ # nslookup u2.
Server:		172.24.255.254
Address:	172.24.255.254:53

Non-authoritative answer:

Non-authoritative answer:
Name:	u2
Address: 172.24.0.3

u2 lookup on u1

Server:		127.0.0.11
Address:	127.0.0.11:53

Non-authoritative answer:

Non-authoritative answer:
Name:	u1
Address: 172.24.0.2

LLM usage

Checklist

  • I have read the contribution guide.
  • The linter passes locally (make lint).
  • The e2e tests of at least one tool pass locally (make test_ctr, make test_nerdctl, make test_docker, make test_crictl).
  • If LLMs were used: I have read the llm policy.

@netlify

netlify Bot commented Jun 28, 2026

Copy link
Copy Markdown

Deploy Preview for urunc ready!

Name Link
🔨 Latest commit 6723c67
🔍 Latest deploy log https://app.netlify.com/projects/urunc/deploys/6a51149ce162730008804ab6
😎 Deploy Preview https://deploy-preview-793--urunc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@alimx07 alimx07 force-pushed the feat/add-docker-dns branch from e43d8cc to 25a6350 Compare June 28, 2026 07:26
On Docker user custom networks the DNS resolver (127.0.0.11) is
loopback only and unreachable by the unikernel guest. Detect this
case per container, expose the resolver via a virtual resolver IP
using tc redirects between the tap and lo + a PREROUTING DNAT,
and rewrite the guest's resolv.conf to point at that IP.

Signed-off-by: Ali Mohamed <amx746@gmail.com>
@alimx07 alimx07 force-pushed the feat/add-docker-dns branch from 25a6350 to a743f29 Compare June 28, 2026 07:44
Signed-off-by: Ali Mohamed <amx746@gmail.com>
@alimx07 alimx07 force-pushed the feat/add-docker-dns branch from a743f29 to 6723c67 Compare July 10, 2026 15:49
@alimx07

alimx07 commented Jul 10, 2026

Copy link
Copy Markdown
Author

Hey @cmainas, I have implemented the changes we discussed during our sync. Could you please take a look and review them? This will allow us to make any necessary changes before we extend this logic to other unikernels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant