From: Markus Geiger <markus.geiger@nielsen.com>
To: musl@lists.openwall.com
Subject: Re: [musl] [BUG] Non-FQDN domain resolving failure on musl-1.2.x
Date: Fri, 24 Jun 2022 19:14:10 +0200 [thread overview]
Message-ID: <CAMsuMPgKYe5aeuGe5C-Km5O=c6JVDhAcPZH5Qxd3TNt+jrJVyA@mail.gmail.com> (raw)
In-Reply-To: <20220624145936.GP7074@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 6580 bytes --]
Sorry: not Amazon DNS – 10.204.109.209 is a BIND server in our network
we've setup to work with our global VPN/DNS.
BUT the strange thing is that the domain lookup works with musl-1.1.24
while with some musl-1.2.x just quits with an error.
a comparison with the docker runs and `sudo tcpdump -v -i docker0 udp port
53 or tcp port 53` did not bring up any diffs except the list of A records
returned is in a different order (which i think is completely normal). the
order of requests is the same
tcpdump from working version:
> bind-us-east-1a.XXXXXXXXXXXXXX.domain > 172.17.0.3.45501: 18685 9/13/8
slack.com. A 3.95.117.96, slack.com. A 34.231.24.224, slack.com. A
54.163.235.119, slack.com. A 54.147.59.169, slack.com. A 34.193.255.5,
slack.com. A 34.204.109.226, slack.com. A 34.225.62.185, slack.com. A
34.203.97.10, slack.com. A 54.92.199.186 (510)
tcpdump from non-working version:
> bind-us-east-1a.XXXXXXXXXXXXXX.domain > 172.17.0.3.59951: 49211 9/13/8
slack.com. A 34.225.62.185, slack.com. A 54.163.235.119, slack.com. A
34.231.24.224, slack.com. A 54.147.59.169, slack.com. A 34.193.255.5,
slack.com. A 34.204.109.226, slack.com. A 54.92.199.186, slack.com. A
3.95.117.96, slack.com. A 34.203.97.10 (510)
Complete log:
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49211+ A? slack.com. (27)
18:56:19.990087 IP (tos 0x0, ttl 64, id 10210, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:20.154990 IP (tos 0x0, ttl 250, id 17825, offset 0, flags [none],
proto UDP (17), length 538)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49211 9/13/8 slack.com. A 34.225.62.185, slack.com. A 54.163.235.119,
slack.com. A 34.231.24.224, slack.com. A 54.147.59.169, slack.com. A
34.193.255.5, slack.com. A 34.204.109.226, slack.com. A 54.92.199.186,
slack.com. A 3.95.117.96, slack.com. A 34.203.97.10 (510)
18:56:20.241377 IP (tos 0x0, ttl 250, id 17846, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:20.241501 IP (tos 0x0, ttl 64, id 10233, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:20.401765 IP (tos 0x0, ttl 250, id 17879, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:20.401831 IP (tos 0x0, ttl 64, id 10247, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:20.563915 IP (tos 0x0, ttl 250, id 17906, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:20.563946 IP (tos 0x0, ttl 64, id 10300, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:20.801072 IP (tos 0x0, ttl 250, id 17915, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:20.801187 IP (tos 0x0, ttl 64, id 10392, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:20.961903 IP (tos 0x0, ttl 250, id 17948, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:22.492127 IP (tos 0x0, ttl 64, id 10410, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:22.745884 IP (tos 0x0, ttl 250, id 18135, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:22.745930 IP (tos 0x0, ttl 64, id 10492, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:22.906904 IP (tos 0x0, ttl 250, id 18171, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:22.906941 IP (tos 0x0, ttl 64, id 10548, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:23.067742 IP (tos 0x0, ttl 250, id 18209, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:23.067773 IP (tos 0x0, ttl 64, id 10559, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:23.228046 IP (tos 0x0, ttl 250, id 18244, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:23.228083 IP (tos 0x0, ttl 64, id 10598, offset 0, flags [DF], proto
UDP (17), length 55)
172.17.0.3.59951 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
49334+ AAAA? slack.com. (27)
18:56:23.388598 IP (tos 0x0, ttl 250, id 18274, offset 0, flags [none],
proto UDP (17), length 55)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.59951:
49334 ServFail 0/0/0 (27)
18:56:24.998168 IP (tos 0x0, ttl 64, id 10759, offset 0, flags [none],
proto UDP (17), length 55)
172.17.0.3.55720 > bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain:
2282+ ANY? slack.com. (27)
18:56:25.199844 IP (tos 0x0, ttl 250, id 18505, offset 0, flags [none],
proto UDP (17), length 538)
bind-us-east-1a.XXXXXXXXXXXXXXXXXXXXXXXXXx.domain > 172.17.0.3.55720:
2282 9/13/8 slack.com. A 34.231.24.224, slack.com. A 34.193.255.5, slack.com.
A 54.163.235.119, slack.com. A 54.92.199.186, slack.com. A 54.147.59.169,
slack.com. A 3.95.117.96, slack.com. A 34.225.62.185, slack.com. A
34.204.109.226, slack.com. A 34.203.97.10 (510)
Thanks for looking into!
Greetings,
Markus
[-- Attachment #2: Type: text/html, Size: 8499 bytes --]
next prev parent reply other threads:[~2022-06-24 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 10:28 Markus Geiger
2022-06-24 14:59 ` Rich Felker
2022-06-24 15:10 ` Jeffrey Walton
2022-06-24 15:15 ` Rich Felker
2022-06-24 17:14 ` Markus Geiger [this message]
2022-06-25 1:56 ` Rich Felker
2022-06-27 11:35 ` Markus Geiger
2022-06-27 14:06 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMsuMPgKYe5aeuGe5C-Km5O=c6JVDhAcPZH5Qxd3TNt+jrJVyA@mail.gmail.com' \
--to=markus.geiger@nielsen.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).