DNS Delegation support (old bug #62)

[mattpascoe]

Delegating subdomains (subdomain.example.com IN NS server.example.com) does not work/show because the name field of an NS record gets cleared in ona/www/winc/list_records.inc.php line 353 and in build_bind.inc.php line 446 only $domain['fqdn'] is used instead of $dnsrecord['name'].$domain['fqdn']

So adding "subdomain.example.com IN NS server.example.com" does work, but shows up as "example.com".

Is there a reason for this behavior?

bziller

I'm not able to recreate this on my end. It seems to be working for me.. Please explain in a bit more detail the steps you use to set it up.

The reason it does not use $dnsrecord['name'].$domain['fqdn'] is that NS records only store the domain information and not the host/name portion. A records for example are a host and a domain together to get an FQDN. NS records leave the name field blank in the database and only store the domain information.

you should have a domain in your system as example.com then a second domain defined as subdomain.example.com. Then when you add a domain server assignment or you manually create the NS record it will point the subdomain.example.com domain to the A record server.example.com as an NS type.

Lets see if we can get the steps in order so I can try and duplicate on my side and see whats up.

Thanks.
Comment by Bernd Ziller (bziller) - Monday, 28 September 2009, 11:32 GMT
Since I'm not responsible for subdomain.example.com, it doesn't help to add this subdomain to ona, because this way there will be no NS entry in example.com delegating subdomain to server.example.com.
So in this case the NS record has the need to store the name field.

I need a "subdomain.example.com IN NS server.example.com" in domain example.com.

I currently can't reproduce this (adding "subdomain.example.com"). I was quite sure I didn't mess with the DB in the first place, but it looks like I did ;)
At the moment I'm trying to add the needed behavior into ona.
Comment by Matt Pascoe (matt) - Wednesday, 30 September 2009, 20:12 GMT — Edit — Delete
I would suggest that even though you are not responsible for subdomain.example.com that you still add the domain to ONA. It is referential only and you would not need to add any more records or data to it. Once it is added then you can point at it for NS records. You can simply click the "add dns record" link and create the NS record that way.

The alternate way of doing this is with zone trailer files. It is something I've not fully built into the BIND build code yet but it will be coming. In my tinydns build code I already have it implemented. Basically it is a file that you can define for each zone that gets appended to the data extracted from ONA. It will allow you to define records in the zone that ONA may not support. In this case, ONA should support the record properly but you may not want to define the subdomain.example.com zone in your system.

Hope that helps.