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

A Name.com TXT entry produces quoted value #3259

Open
tkurki opened this issue Dec 17, 2024 · 3 comments · May be fixed by #3260
Open

A Name.com TXT entry produces quoted value #3259

tkurki opened this issue Dec 17, 2024 · 3 comments · May be fixed by #3260

Comments

@tkurki
Copy link

tkurki commented Dec 17, 2024

Describe the bug
This configuration produces a quoted TXT record value:
image

If I manually remove the quotes in name.com UI subsequent push operations do nothing .

To Reproduce
See linked repo.

Log of 2 push runs:

CONCURRENTLY gathering 0 zone(s)
SERIALLY gathering 1 zone(s)
Serially Gathering: "signalk.org"
******************** Domain: signalk.org
1 correction (name.com)
#1: + CREATE TXT _atproto.signalk.org "did=did:plc:b6o3a5sifu6lp7if47yabyvp" ttl=300
SUCCESS!
Done. 1 corrections.

====> THE VALUE APPEARS QUOTED. MANUALLY REMOVED QUOTES FROM THE VALUE HERE <====

signalk/dns(main|✔) %   ./run.sh push
CONCURRENTLY gathering 0 zone(s)
SERIALLY gathering 1 zone(s)
Serially Gathering: "signalk.org"
******************** Domain: signalk.org
Done. 0 corrections.

Expected behavior
The value is created without quotes. All push operations effect changes so that the actual dns is like the donscontrol configuration.

DNS Provider

  • name.com

Additional context
The record is for Bluesky.social domain verification.

@tlimoncelli
Copy link
Contributor

This sounds a lot like https://docs.dnscontrol.org/developer-info/testing-txt-records

The bad news is that the NAMEDOTCOM provider doesn't have a maintainer at this time.

The good news is that while writing some tips about how to debug this on your own, I think I found the bug.

Can you build #3260 and see if that fixes the problem?

@tkurki
Copy link
Author

tkurki commented Dec 17, 2024

If you tell me how 😁 - pointers?

@tlimoncelli
Copy link
Contributor

hi @tkurki ! Glad to help. I put the instructions in #3260 (comment)

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

Successfully merging a pull request may close this issue.

3 participants