Skip to content

Prevent upstream DNS queries of NCSI domain names#102

Merged
mplattu merged 2 commits intomainfrom
fix/avoid-ncsi-resolving-ipv6
Apr 13, 2026
Merged

Prevent upstream DNS queries of NCSI domain names#102
mplattu merged 2 commits intomainfrom
fix/avoid-ncsi-resolving-ipv6

Conversation

@mplattu
Copy link
Copy Markdown
Contributor

@mplattu mplattu commented Apr 9, 2026

Without setting upstream DNS servers to none, the dnsmasq resolves the IPv6 addresses. In the case of NCSI servers the upstream server returns CNAME-record, which is resolved by dnsmasq to 127.0.0.1.

When client tries to get the valid NCSI response from 127.0.0.1 it obviously fails which causes NCSI to switch the network.

@mplattu mplattu requested a review from linuswillner April 9, 2026 10:09
@mtreinik
Copy link
Copy Markdown
Contributor

mtreinik commented Apr 9, 2026

Kokeillaan tämän sijasta:

  • estää dnsmasq:ia jakelemasta IPV6-osoitteita
  • lisätä IPV6-muotoinen null-route ::

This setting tells dnsmasq not to process IPv6 DNS queries
for NCSI domains.

Without this, dnsmasq returns randomly (?) response from
IPv4 response from "host-record" or CNAME value from IPv6 query
made to upstream. Later, the client resolves CNAME response to
null-route (`address=/#/0.0.0.0`) which makes Windows clients to
search NCSI responses from localhost.
@mplattu mplattu force-pushed the fix/avoid-ncsi-resolving-ipv6 branch from 8f25516 to 0e2c8fc Compare April 10, 2026 10:28
@mplattu
Copy link
Copy Markdown
Contributor Author

mplattu commented Apr 10, 2026

The discussed solutions did not result to desired outcome, but the IPv6 null-route :: could be used with host-record.

Added also null-route to unknown IPv6 addresses, as discussed elsewhere.

@mplattu mplattu merged commit 5549b44 into main Apr 13, 2026
1 check passed
@mplattu mplattu deleted the fix/avoid-ncsi-resolving-ipv6 branch April 13, 2026 08:50
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.

3 participants