mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 09:25:56 +03:00
[GH-ISSUE #428] Permanent error on AAAA request #148
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#148
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pavlyuts on GitHub (Dec 7, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/428
Originally assigned to: @mageddo on GitHub.
What is Happening / What is expected
DPS logs fault, associated to AAAA request on container name
Log entry:
To reproduce:
dig @127.0.0.1 test.docker AAAADPS config file
Specs
@sneusse commented on GitHub (Dec 13, 2023):
same here, can we disable AAAA in some way?
@mageddo commented on GitHub (May 1, 2024):
Hey thanks for the report.
I got this, the issue is caused when beyond the container, your hostmachine or the docker engine also hasn't an associated IPV6, it will try to use the host machine IPV6 but it hasn't one associated, null is returned:
Then the error occurs
update
The bug is here,
.findFirst()will throw a NPE when there is a null value in the collection, which is the case, the host machine IP produced in.mapis null.github.com/mageddo/dns-proxy-server@17b0c0043d/src/main/java/com/mageddo/dnsproxyserver/docker/ContainerSolvingService.java (L50)I'm working on the fix
@mageddo commented on GitHub (May 1, 2024):
No sure, it's related to your OS and DNS client, it's asking for AAAA records then DPS will answer them, so you have to disable the AAAA queries on the requester, don't know how.
@mageddo commented on GitHub (May 1, 2024):
Just to make it clear, this issue won't make DPS stop of working, just will produce a lot of unnecessary logs
@mageddo commented on GitHub (May 1, 2024):
Version was released, you can reopen if the issue persists somehow