Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLOUDFLAREAPI: LOC supported by CF but not by integration #2798

Open
ConnorMcF opened this issue Jan 15, 2024 · 3 comments
Open

CLOUDFLAREAPI: LOC supported by CF but not by integration #2798

ConnorMcF opened this issue Jan 15, 2024 · 3 comments

Comments

@ConnorMcF
Copy link

Describe the bug
The LOC record is supported by Cloudflare, but not by the integration.

providers.CanUseLOC: providers.Cannot(),

Expected behavior
Cloudflare supports LOC records, I would assume that the DNSControl integration would also support them.
I'm hoping this may be as simple as switching Cannot to Can.

LOC is listed as a valid type in the Cloudflare API: https://developers.cloudflare.com/api/operations/dns-records-for-a-zone-list-dns-records

DNS Provider

  • Cloudflare
@cafferata
Copy link
Collaborator

I'm hoping this may be as simple as switching Cannot to Can.

That's right! Do you want to prepare a GitHub pull request yourself? Or shall I do that for you? ☺️

@cafferata
Copy link
Collaborator

cc: Maintainer CLOUDFLAREAPI @tresni for visibility.

@cafferata
Copy link
Collaborator

type string
Record type.

Allowed values: A, AAAA, CAA, CERT, CNAME, DNSKEY, DS, HTTPS, LOC, MX, NAPTR, NS, PTR, SMIMEA, SRV, SSHFP, SVCB, TLSA, TXT, URI

Deeplink

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants