I just tested this.. Created a A record in my zone I have on he.net - its my ipv6 subzone I had pointed to HE for cert tests, but sure can create a A record in it.
So I did it here from work, and it put in my work address at first, checked off to enable my ddns -- then hit that arrows and generated key. Then put in the test.ipv6.mydomain.net as host and username on pfsense and put in the generated key from he as the password.
And shazam it updated my he record.
So here are screenshots showing it working.
make sure you use the he.net vs the he tunnelbroker in the dropdown.
Guess its possible its broke in 2.0.1 - I run the development code - I would think you should be too if playing with he.net IPv6 tunnels on pfsense.
built on Fri Nov 25 17:45:38 EST 2011
Even just did a query to make sure it works -
; <<>> DiG 9.7.3 <<>> test.ipv6.snipped.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38129
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;test.ipv6.snipped.net. IN A
;; ANSWER SECTION:
test.ipv6.snipped.net. 300 IN A 24.13.xxx.20
From the errors you have in your log about binding, etc. You prob better of troubleshooting your issue on the pfsense forums.. Sure looks like there is nothing wrong with the he system to me. And it works on my pfsense, but again I am running 2.1 and run gitsyncs prob once a week to keep up with the lastest code -- maybe there is something broke in the 2.0.1 that has not been fixed yet?