• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

subdomain for my own bind9 server

Started by rakogels, June 25, 2026, 01:27:57 AM

Previous topic - Next topic

rakogels

Hi all,

I am having issues setting up DNS for my subdomain, using my own bind9 server.
It seems that the delegation part is not working.

This is what I have done:
1. In parent zone (example.com) I added a NS records for the subdomain delegation:

Name: sub.example.com
Type: NS
Value: ns1.sub.example.com

2. Added glue record in parent zone (example.com):
Name: ns1.sub.example.com
Type: A, Value: MY_SERVER_PUBLIC_IP

3. Added sub.example.com via he.net webportal to my main domain (example.com)
Note that the webportal tells me to add a TXT record with name dnshenet-key and value they provided.
I added this record to my bind config for this subdomain.

Any suggestions why this is not working?

Thanks.


snarked

Step 3 doesn't make sense.  Action 3 you took implies that HE's servers are primary for the zone.  However, actions 1 & 2 plus your opening statement implies that your private server is primary and HE's servers are secondary.  Please restate your question if this is wrong.

One does not add any RRs in HE's web interface for secondary zones; only name server addresses (names get resolved to addresses) and a TSIG key (if used).

If HE asked you to add a TXT record, that goes into the zone file, not the server configuration file.

rakogels

Thanks Snarked. By removing sub.example.com from he.net it started to work.
sub.example.com is now served by my bind dns server while example.com is served by he.net as required.

I guess I got confused with the assumption that you need to add a subdomain to he.net first and in that subdomain you need to put the details for your own DNS server.