You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
api: dnsIssues related to the googleapis/nodejs-dns API.🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
When importing zone files (bind format) using zone.import, we call Record.fromZoneRecord_ on each line. However, when you have multiple of the same record that should in be a single result set (i.e. MX records), it actually creates a record set per line, which doesn't result in the correct zone being created.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
api: dnsIssues related to the googleapis/nodejs-dns API.🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
From @timwsuqld on August 22, 2017 4:21
Environment details
Steps to reproduce
When importing zone files (bind format) using
zone.import
, we callRecord.fromZoneRecord_
on each line. However, when you have multiple of the same record that should in be a single result set (i.e. MX records), it actually creates a record set per line, which doesn't result in the correct zone being created.The
resourceRecordSets
rrdatas
should be a list (https://cloud.google.com/dns/api/v1/resourceRecordSets#resource) of all the records, not multiple resourceRecordSets. The result is only the last MX record is imported.This would probably also cause problems if for example you have multiple TXT records, or multiple A records.
Copied from original issue: googleapis/google-cloud-node#2552
The text was updated successfully, but these errors were encountered: