OctoDNS Sync Limitation with More Than 500 DNS Records

[K3RM1T-CYBER]

Hello !

It seems that the module does not support managing more than 500 DNS records for a domain.

In my domain.yml file, I have 721 DNS entries. When I run octodns-sync, I can see the following message:
YamlProvider[yaml] populate: found 721 records, exists=True

However, during the dry-run, it attempts to create 221 records, even though they are already present on the Gandi side.

It looks like there is a limitation or an issue with handling more than 500 records.

Has anyone else experienced this? Is there a known limitation or configuration I might be missing?

Thank you for your help!

[ross]

I assume the client's record listing method will need to add support for pagination. The default must be 500.

octodns-gandi/octodns_gandi/__init__.py

Lines 82 to 104 in 1c0e0fe

	def zone_records(self, zone_name):
	records = self._request(
	'GET', f'/livedns/domains/{zone_name}/records'
	).json()
	for record in records:
	if record['rrset_name'] == '@':
	record['rrset_name'] = ''
	# Change relative targets to absolute ones.
	if record['rrset_type'] in [
	'ALIAS',
	'CNAME',
	'DNAME',
	'MX',
	'NS',
	'SRV',
	]:
	for i, value in enumerate(record['rrset_values']):
	if not value.endswith('.'):
	record['rrset_values'][i] = f'{value}.{zone_name}.'
	return records

I don't have access to gandi, but happy to review PRs.

[K3RM1T-CYBER]

#49

[K3RM1T-CYBER]

Hello, do you have any information on the date when a new tag with pagination management will appear?

[ross]

No specific date currently planned, but I try to give it some time and avoid releasing things for every single feature. You can ping a specific SHA in the meantime. See https://github.com/octodns/octodns-gandi?tab=readme-ov-file#shas.