Repository navigation
Rename class DnsRecord #779
Description
Activity
- added this to the milestone
on Mar 23, 2016 Errr - really? I don't love this... can we debate a bit more first.... ?
- changed the title
[-]Rename class DnsRecord to ResourceRecordSet[/-][+]Rename class DnsRecord[/+]on Mar 23, 2016 I renamed the issue. The final name is to be decided after some discussion. The suggestions are DnsRecordSet and ResourceRecordSet.
I slightly prefer DnsRecordSet over ResourceRecordSet, but I'm fine with either. RecordSet would be shorter; do you think it's a clear enough name?
Errr - really? I don't love this... can we debate a bit more first.... ?
The issue is that what we call
DnsRecorddoes not actually represent one DNS record but rather a set of records (and therefore is called in the underlying service APIResourceRecordSet).BTW, it looks like this long name was adopted by gcloud-python though node choose Record (which I personally think is wrong).
I think the main point is to indicate that it is a set rather than an individual item and therefore my ordered preference would be:
RecordSet,DnsRecordSet,ResourceRecordSet.
With a much stronger preference to the first.After some discussion both here and internally, including the input from the DNS team, we will rename to
RecordSet.- added 4 commits that reference this issue
on Mar 23, 2016 14 remaining items
- added 2 commits that reference this issue
on Feb 1, 2023 - added a commit that references this issue
on Dec 22, 2025 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Mar 11, 2026 - added a commit that references this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 30, 2026 - added a commit that references this issue
on Apr 1, 2026 - added a commit that references this issue
on Jul 13, 2026
This was pointed out by the DNS team.