Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support DNS queries for the SVCB record type #615

Open
frcroth opened this issue Jan 31, 2025 · 2 comments
Open

Support DNS queries for the SVCB record type #615

frcroth opened this issue Jan 31, 2025 · 2 comments

Comments

@frcroth
Copy link

frcroth commented Jan 31, 2025

I am interested in the global distribution of DDR (https://www.rfc-editor.org/rfc/rfc9462.html). DDR uses the SVCB record type, which is not currently supported in Globalping.

A DDR query is simply a SVCB query to the _dns.resolver.arpa address.

With dig, the query can be performed as such:
dig +short SVCB _dns.resolver.arpa @8.8.8.8

It would be great if SVCB could be added to the supported record types for DNS queries.

@jimaek
Copy link
Member

jimaek commented Feb 2, 2025

We could add it, but could you please provide some more details?
Is there any value to these queries being geo distributed? It sounds like you could run these queries from a single machine to all resolvers and get the data you need.
Wouldn't the response always be the same regardless the location?

@frcroth
Copy link
Author

frcroth commented Feb 2, 2025

DDR is used in the communication with the locally configured resolver (usually configured by the ISP). These resolvers may not be accessible globally and when scanning from one vantage point we can not access them nor know what resolver is actually used with the client's configuration.
That's why scanning from different vantage points would give a more realistic and useful impression of how DDR is used and deployed.

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

No branches or pull requests

2 participants