question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Route53 failing to list CNAME records only.

See original GitHub issue
>>> response = client.list_resource_record_sets(HostedZoneId=zone_id, StartRecordType='CNAME')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/site-packages/botocore/client.py", line 251, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python2.7/site-packages/botocore/client.py", line 537, in _make_api_call
    raise ClientError(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (InvalidInput) when calling the ListResourceRecordSets operation:

When I take out flag StartRecordType='CNAME' all is well. However that is much to verbose for my needs.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
davizuconcommented, May 25, 2018

HI, I see, perhaps how the text is formatted is leading to doubt. Thanks

0reactions
davizuconcommented, May 25, 2018

By the way, If can mention in this part:

StartRecordType (string) – The type of resource record set to begin the record listing from Something like: Requires StartRecordName…

Suggestion of course.

Thanks for your attention.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshoot errors when creating Route 53 resource record ...
The UPSERT is successful only if you originally had a CNAME record and UPSERT to another CNAME record. An error occurred (InvalidChangeBatch) ...
Read more >
Why newly created AWS Route53 records may not resolve
A simple click on the “Create Record” button and you want to check if it works immediately. But trying to resolve the DNS...
Read more >
Route 53 Alias vs CNAME - Jayendra's Cloud Certification Blog
CNAME records can be used only for subdomains. Route 53 automatically recognizes changes in the resource record sets that the alias resource record...
Read more >
Why is the Route 53 Alias record for an Elastic Load Balancer ...
... Knowledge Center article with this video: https://aws.amazon.com/premiumsupport/knowledge-center/elb- route-53 -unresolved- alias -recor...
Read more >
How ALIAS records can reduce initial load times for your website
The ideas of avoiding single points of failure and being resilient to ... ALIAS records are only usable when Route53 manages your domain....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found