unbound: add CNAME support

opnsense / core

OPNsense GUI, API and systems backend

https://opnsense.org/

BSD 2-Clause "Simplified" License

3.35k stars 752 forks source link

unbound: add CNAME support #1041

Closed fichtner closed 7 years ago

fichtner commented 8 years ago

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

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

AdSchellevis commented 8 years ago

@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 commented 8 years ago

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 commented 7 years ago

don't really need this it seems

MarkNBroadhead commented 5 years ago

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

fichtner commented 5 years ago

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

MarkNBroadhead commented 5 years ago

@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).

fichtner commented 5 years ago

Nope.

https://github.com/pfsense/pfsense/search?utf8=✓&q=cname&type= https://forum.netgate.com/topic/110680/dns-cname-records-posible-with-unbound/5

MarkNBroadhead commented 5 years ago

@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.

fichtner commented 5 years ago

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