Emulator -dns-server option does not work after API 31 [249366543]

Fixed

Bug

Status Update

No update yet.

Description

ws...@gmail.com

created issue #1

Sep 28, 2022 12:57AM

DESCRIBE THE ISSUE IN DETAIL: The emulator CLI's -dns-server option does not seem to work on API 31 or newer.

STEPS TO REPRODUCE:

Run a local dns server and log queries: dnsmasq -dq
Start an API 31 emulator: emulator -avd emulator31 -dns-server 127.0.0.1
Resolve a domain: adb shell ping www.reddit.com
dnsmasq does not show that domain in the log.

However, on API 30, these same steps will result in the dnsmasq showing the queries to reddit.com:

dnsmasq: query[A] www.reddit.com from 127.0.0.1
dnsmasq: forwarded www.reddit.com to <ip>
dnsmasq: reply www.reddit.com is <CNAME>
dnsmasq: reply reddit.map.fastly.net is <ip>

We need to override some DNS entries in order to test our app in environments that do not have external internet access, but it stopped working in API 31 or newer.

Comments

ws...@gmail.com <ws...@gmail.com> #2Sep 28, 2022 04:44PM

This is using emulator version 31.3.10

pa...@google.com <pa...@google.com> Sep 29, 2022 12:52AM

Assigned to an...@google.com.

ws...@gmail.com <ws...@gmail.com> #3Sep 29, 2022 01:03AM

Probably very related to https://issuetracker.google.com/issues/229752137

Another quirk of emulator network backend to note, Pre-API 31, WiFi and radio networks share the same network backend but since API 31, they use separate network backend (both are using user-mode by default).

bo...@google.com <bo...@google.com> Oct 5, 2022 06:53PM

Reassigned to wd...@google.com.

wd...@google.com <wd...@google.com> #4Oct 14, 2022 03:03PM

Accepted by wd...@google.com.

RE#3 Thanks for reporting this bug to me. We do have 2 instances of slirp backend and we only initialize dns for one of the SLIRP instance. This is where the bug happens. Code. Let me fix this issue and provide you with a version of emulator for testing purpose. Thanks!

wd...@google.com <wd...@google.com> #5Oct 17, 2022 07:45PM

Marked as fixed.

CL merged.

jo...@inspiretek.io <jo...@inspiretek.io> #6Oct 18, 2022 02:44AM

Where can we get a version of the merged fix as well? or where can we monitor it? thanks!

wd...@google.com <wd...@google.com> #7Oct 18, 2022 02:27PM

RE#6 Hi Joshua, we will release the fix in the next canary release (weekly schedule). I will also make sure the fix get merged into the next stable release but it might take no longer.

wd...@google.com <wd...@google.com> #8Oct 27, 2022 05:59PM

RE#6 As I have confirmed, the fix is in 31.3.13 stable release.