Skip to content

coredns: request must return both IPv6 and IPv4 for recordtype ANY#250

Open
flouthoc wants to merge 1 commit into
containers:mainfrom
flouthoc:resolver-any-request
Open

coredns: request must return both IPv6 and IPv4 for recordtype ANY#250
flouthoc wants to merge 1 commit into
containers:mainfrom
flouthoc:resolver-any-request

Conversation

@flouthoc

@flouthoc flouthoc commented Nov 4, 2022

Copy link
Copy Markdown
Collaborator

Aardvark-dns must return both IPv6 and IPv4 if the DNS request has record type ANY instead of A or AAAA record type.

Closes: #249

@flouthoc

flouthoc commented Nov 4, 2022

Copy link
Copy Markdown
Collaborator Author

/hold this needs dedicated tests

@openshift-ci

openshift-ci Bot commented Nov 4, 2022

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Nov 4, 2022

@Luap99 Luap99 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM when test is added

Aardvark-dns must return both `IPv6` and `IPv4` if the DNS request has
record type `ANY` instead of `A` or `AAAA` record type.

Closes: containers#249

Signed-off-by: Aditya R <arajan@redhat.com>
@openshift-merge-robot

Copy link
Copy Markdown
Collaborator

@flouthoc: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Luap99

Luap99 commented Jan 24, 2023

Copy link
Copy Markdown
Member

@flouthoc What is the state here? Can you add a test?

@Luap99

Luap99 commented May 10, 2023

Copy link
Copy Markdown
Member

@flouthoc ping, is still still wanted?

@flouthoc

Copy link
Copy Markdown
Collaborator Author

@Luap99 Not wanted by anybody but I just found it while playing, let me see if i can still repro this and the patch fixes the issue or not, I think there were some edgecase which i was hitting last time playing with this.

@tripougnif

Copy link
Copy Markdown

@Luap99 Not wanted by anybody but I just found it while playing, let me see if i can still repro this and the patch fixes the issue or not, I think there were some edgecase which i was hitting last time playing with this.

Nextcloud is doing ANY requests. I don't know if this is something they should fix on their end, but since other resolvers return A and AAAA records on ANY requests, I'd say this fix is needed.

@tripougnif

tripougnif commented Jan 31, 2024

Copy link
Copy Markdown

There are actually to issues. The first one is resolved with this PR. The second is aardvark-dns not being bound to TCP and that ANY queries are going through TCP by default.

@Luap99

Luap99 commented May 13, 2025

Copy link
Copy Markdown
Member

@flouthoc Still interested in finishing this?
In the meantime tcp support was added and I reworked parts of this code heavily but I guess adding this should still be simple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dns: inbuilt resolver should return both IPv6 and IPv4 records if request type is ANY

4 participants