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

[Feature Request] Autohints for https #911

Open
Kofl opened this issue Apr 29, 2024 · 5 comments
Open

[Feature Request] Autohints for https #911

Kofl opened this issue Apr 29, 2024 · 5 comments

Comments

@Kofl
Copy link

Kofl commented Apr 29, 2024

Hi,

it would be awesome if autohins for https would be supported similar to the PowerDNS idea.

Would increase the DNS resolution speed and at the same time not increase the administrative burden:

www.example.org IN HTTPS 1 . ipv4hint=auto

in DNS zone resolves to DNS query as:

www.example.org. 3600 IN HTTPS 1 . ipv4hint=192.0.2.1

Ref: https://doc.powerdns.com/authoritative/guides/svcb.html

Thanks

@ShreyasZare
Copy link
Member

Thanks for the feature request. Will get that added soon.

@ShreyasZare
Copy link
Member

I did some analysis on this feature and it seems that it would be difficult to add support for it. The main issue is that since this is a proprietary feature, there is no standard wire format for this option defined. Which means, this record cannot be serialized to sent over wire and thus it wont work with zone transfers to allow secondary zones to sync records. Even if some proprietary wire format was define, it would only work with Technitium DNS as the secondary server and would fail to work with other 3rd party DNS server software.

The other issue with it is that since this feature essentially makes the record dynamic, it creates issue with DNSSEC signing support as the records are signed in advance. Dynamic record signing (online signing) is not possible with current DNSSEC implementation.

Also, since the DNS server is already returning A and AAAA records in the additional section, adding the same info as hints would be redundant. The client app will already be processing the additional A and AAAA records since IP hints have lower priority and are only to be used if A or AAAA records were not available immediately.

@Kofl
Copy link
Author

Kofl commented May 14, 2024

Hi,

thanks for looking into it.

As far as I understand the documentation for zone transfer they resolve the value and transfer via the zone transfer only:
www.example.org. 3600 IN HTTPS 1 . ipv4hint=192.0.2.1

For zone signing at the end only the real values would be signed and ipv4hint=auto never be visible outside to any DNS client / DNS zone transfer?

@ShreyasZare
Copy link
Member

Thanks for the response. I reread their docs and yes they resolve the address before writing to wire so zone transfer works normally. Not sure how they are doing signing, may be they have online signing support which is not available in Technitium DNS.

I guess, this can be implemented such that whenever the SVCB/HTTPS record is added/updated, it will check for the relevant A/AAAA records in the zone and update it immediately. And when any A/AAAA record is added/updated, it checks to see if there are any SVCB/HTTPS records and then update the hints. This way it would be possible to sign the records in advance. Will think on this for a while to get how it could be implemented.

@Kofl
Copy link
Author

Kofl commented May 15, 2024

Thanks for sticking to the topic and clarifying the open parts, no hurry from my side. Would be a great addition.

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