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

unbound: add CNAME support #1041

Closed
fichtner opened this issue Jun 27, 2016 · 9 comments
Closed

unbound: add CNAME support #1041

fichtner opened this issue Jun 27, 2016 · 9 comments
Assignees
Labels
feature Adding new functionality
Milestone

Comments

@fichtner
Copy link
Member

fichtner commented Jun 27, 2016

PTR was also asked for, maybe we should make the framework more flexible...

via: https://forum.opnsense.org/index.php?topic=3246.0

@fichtner fichtner added the feature Adding new functionality label Jun 27, 2016
@fichtner fichtner added this to the 17.1 milestone Jun 27, 2016
@fichtner fichtner self-assigned this Jun 27, 2016
@AdSchellevis
Copy link
Member

@fichtner we can include the unbound cname tag, but its not very likely that it will actually work. From what I can find.

The only time your entry will be returned is if the client queries for a CNAME, which in practice means it'll probably be returned quite rarely

(source https://www.bentasker.co.uk/documentation/linux/279-unbound-adding-custom-dns-records)

The information on the unbound mailing list:
http://unbound.net/pipermail/unbound-users/2009-March/000509.html

Add the tag any way? or close the issue?

@fichtner
Copy link
Member Author

Let's keep it on 17.1, wait for feedback. It should be possible to add this in the advanced settings to collect valuable information of how that works out from the actual client side and that will likely decide in the end :)

@fichtner
Copy link
Member Author

don't really need this it seems

@MarkNBroadhead
Copy link

Lack of alias/cname support in unbound is the only thing keeping me on pfsense. I'd really like this to be implemented.

@fichtner
Copy link
Member Author

fichtner commented Feb 1, 2019

@MarkNBroadhead Can you point me to the Unbound CNAME implementation in pfSense please?

@MarkNBroadhead
Copy link

MarkNBroadhead commented Feb 20, 2019

@fichtner The implementation should be in services_unbound_host_edit.php in the section, "Additional Names for this Host", which allows configuration of aliases (cnames).

@MarkNBroadhead
Copy link

@fichtner You are right. PfSense's implementation does not create CNAMES although it appears to do just that. It create multiple A records all tied to one IP address in configuration and in the UI, creating the convenience of a CNAME without CNAME support. I will open a different feature request for this to be added as it is terribly useful.

Your search in source for "cname" returns no results because the PfSense implementation referred to these other hosts "aliases". The implementation is in the file I linked.

image

@fichtner
Copy link
Member Author

@MarkNBroadhead we have this as well :)services: unbound dns: overrides

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality
Development

No branches or pull requests

3 participants