starred/dns-proxy-server-mageddo

Fork 0

mirror of https://github.com/mageddo/dns-proxy-server.git synced 2026-04-25 09:25:56 +03:00

[GH-ISSUE #309] v3 regression: Wild card domain resolution appears to fail unlike in v2 #109

New issue

Closed

opened 2026-02-26 04:34:04 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 04:34:04 +03:00

Owner

Originally created by @addshore on GitHub (Feb 24, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/309

Originally assigned to: @mageddo on GitHub.

What is Happening

I am trying on the v3 betas in https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/330
This drops right in the place of my usage of v2 without any additional changes https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/330/diffs#d632a42138acb9bcc35a4d2e3eee040758ab84cc_6_6
And one of my end to end tests is failing https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/69627

Specifically....
A dps service is created in a docker-compose setup with a fixed IP on a dps network and with access to the docker socket
This DNS service is then used by all the contianer in the setup, such as mediawiki-fresh which specifies the dns service by its IP
As part of the test this service tries to resolve default.mediawiki.mwdd, but it fails

[0-0] Error in "Page."before all" hook for "should be previewable @daily""
Error: getaddrinfo ENOTFOUND default.mediawiki.mwdd
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)
[0-0] RETRYING in chrome - /tests/selenium/specs/page.js
[0-0] RUNNING in chrome - /tests/selenium/specs/page.js
[0-0] Error in "Page."before all" hook for "should be previewable @daily""
Error: getaddrinfo ENOTFOUND default.mediawiki.mwdd
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)
[0-0] FAILED in chrome - /tests/selenium/specs/page.js (1 retries)

The host is correctly resolved outside of a container, but when inside it appears to struggle or fail?
(Though this is perhaps due to the fact I use *.localhost)?

The service that should be resolved to is mediawiki-web, where a VIRTUAL_HOST env var is used.

What is expected

A container that uses DPS as the DNS server should be able to resolve this wild card hostname.

Originally created by @addshore on GitHub (Feb 24, 2023). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/309 Originally assigned to: @mageddo on GitHub. ### What is Happening I am trying on the v3 betas in https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/330 This drops right in the place of my usage of v2 without any additional changes https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/330/diffs#d632a42138acb9bcc35a4d2e3eee040758ab84cc_6_6 And one of my end to end tests is failing https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/69627 Specifically.... A [dps service](https://gitlab.wikimedia.org/repos/releng/cli/-/blob/03104cb9fd8d45403f10e70c5d4b09de694ee168/internal/mwdd/files/embed/base.yml#L6) is created in a docker-compose setup with [a fixed IP on a `dps` network](https://gitlab.wikimedia.org/repos/releng/cli/-/blob/03104cb9fd8d45403f10e70c5d4b09de694ee168/internal/mwdd/files/embed/base.yml#L12) and [with access to the docker socket ](https://gitlab.wikimedia.org/repos/releng/cli/-/blob/03104cb9fd8d45403f10e70c5d4b09de694ee168/internal/mwdd/files/embed/base.yml#L9) This DNS service is then used by all the contianer in the setup, [such as `mediawiki-fresh`](https://gitlab.wikimedia.org/repos/releng/cli/-/blob/03104cb9fd8d45403f10e70c5d4b09de694ee168/internal/mwdd/files/embed/mediawiki-fresh.yml#L8) which [specifies the dns service by its IP](https://gitlab.wikimedia.org/repos/releng/cli/-/blob/03104cb9fd8d45403f10e70c5d4b09de694ee168/internal/mwdd/files/embed/mediawiki-fresh.yml#L17) As part of the test this service tries to resolve `default.mediawiki.mwdd`, but it [fails](https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/69627#L551) ``` [0-0] Error in "Page."before all" hook for "should be previewable @daily"" Error: getaddrinfo ENOTFOUND default.mediawiki.mwdd at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26) [0-0] RETRYING in chrome - /tests/selenium/specs/page.js [0-0] RUNNING in chrome - /tests/selenium/specs/page.js [0-0] Error in "Page."before all" hook for "should be previewable @daily"" Error: getaddrinfo ENOTFOUND default.mediawiki.mwdd at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26) [0-0] FAILED in chrome - /tests/selenium/specs/page.js (1 retries) ``` The host is [correctly resolved outside of a container](https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/69627#L457), but when inside it appears to struggle or fail? (Though this is perhaps due to the fact I use *.localhost)? The service that should be resolved to is `mediawiki-web`, [where a `VIRTUAL_HOST` env var is used.](https://gitlab.wikimedia.org/repos/releng/cli/-/blob/03104cb9fd8d45403f10e70c5d4b09de694ee168/internal/mwdd/files/embed/mediawiki.yml#L40) ### What is expected A container that uses DPS as the DNS server should be able to resolve this wild card hostname.

kerem

2026-02-26 04:34:04 +03:00

closed this issue
added the
bug

confirmed
labels

kerem commented

2026-02-26 04:34:04 +03:00

Author

Owner

@mageddo commented on GitHub (Feb 25, 2023):

Wildcards were supposed to be working, I will do some tests

@mageddo commented on GitHub (Feb 25, 2023): Wildcards were supposed to be working, I will do some tests

kerem commented

2026-02-26 04:34:04 +03:00

Author

Owner

@mageddo commented on GitHub (Feb 25, 2023):

Found the cause

Docker container wasn't solving from env when the names weren't separated by , (spaces before and after the comma were needed)

@mageddo commented on GitHub (Feb 25, 2023): Found the cause > Docker container wasn't solving from env when the names weren't separated by ` , ` (spaces before and after the comma were needed)

kerem commented

2026-02-26 04:34:04 +03:00

Author

Owner

@mageddo commented on GitHub (Feb 25, 2023):

Minimal reproducible example

@mageddo commented on GitHub (Feb 25, 2023): [Minimal reproducible example][1] [1]: https://github.com/mageddo/dns-proxy-server/tree/c1dcfe5/examples/wildcards

kerem commented

2026-02-26 04:34:04 +03:00

Author

Owner

@mageddo commented on GitHub (Feb 25, 2023):

Github automatically closed the issue, please reopen if the issue persists

@mageddo commented on GitHub (Feb 25, 2023): Github automatically closed the issue, please reopen if the issue persists

kerem commented

2026-02-26 04:34:04 +03:00

Author

Owner

@addshore commented on GitHub (Feb 26, 2023):

It looks like I can confirm that wildcards are now working in my e2e tests using the latest beta.
There is another issue, I'll investigate and try to write a ticket if I figure out what is up.

@addshore commented on GitHub (Feb 26, 2023): It looks like I can confirm that wildcards are now working in my e2e tests using the latest beta. There is another issue, I'll investigate and try to write a ticket if I figure out what is up.

kerem referenced this issue

2026-02-26 04:34:42 +03:00

[PR #109] [CLOSED] Customizable hostname #275