DNS Resolver TXT Comment Support
-
TXT Comment support: Provides the ability to view comments associated with static host entries using DNS. To view these comments one would simply execute the following command:
host -t TXT host_entry <pfsense_ip>host_entry has no TXT recordBut the host_entry in question is a static DHCP entry and does have an associated description. I see no place to enter a comment for static DHCP entries though. So I am left to assume that the term comment here is referring to the static DHCP description entry. That being the case it would seem this feature is not working.</pfsense_ip>
-
bump
Does the Unbound TXT Comment support option work?
DNS Resolver configuration page option states this:
TXT Comment Support
If this option is set, then any descriptions associated with Host entries and DHCP Static mappings will create a corresponding TXT record.DNS Resolver configuration help page states this:
TXT Comment support:
Provides the ability to view comments associated with static host entries using DNS. To view these comments one would simply execute the following command:
host -t TXT host_entry <pfsense_ip>All my DHCP static mappings have descriptions. But all I get from a text record query is, … has no TXT record</pfsense_ip> -
I could not get TXT comment support working for host entries nor DHCP static mappings as documented
https://doc.pfsense.org/index.php/Unbound_DNS_Resolver
But could create txt records using Advance
server:
local-data: "my.host.entry IN TXT 'my descriptive text"$ host -t TXT my.host.entry
my.host.entry descriptive text "my descriptive tex" -
I could not get TXT comment support working for host entries nor DHCP static mappings as documented
https://doc.pfsense.org/index.php/Unbound_DNS_Resolver
So either we are both doing something wrong or it doesn't work.
Thanks for the confirmation.
2.2.2-RELEASE (i386)
built on Mon Apr 13 20:10:33 CDT 2015
FreeBSD 10.1-RELEASE-p9 -
yeah seems to be broken.. and bit confusing because under the wording of the description field
You may enter a description here for your reference (not parsed).
So which is it, check and creates txt from this, or its not parsed? Seems its not parsed..
