StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-09-20 14:56:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

DOCS: Update testing-txt-records.md (#2138)

Browse source 
Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>
This commit is contained in:
Paul Dee 2023-03-12 18:22:56 +01:00 committed by GitHub
parent e9adccd3a4
commit bfad9d68a0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
documentation/testing-txt-records.md
View file

@ -1,14 +1,14 @@
# TXT record testing
We recently discovered a strange but with processing TXT records and
double-quotes. Sadly we haven't been able to determine a way to test this
automatically. Therefore, I've written up this methodology.
double-quotes. Sadly we haven't been able to determine a way to test this
automatically. Therefore, I've written up this methodology.
# The problem
The problem relates to TXT records that have a string with quotes in them.
If a user creates a TXT record who's contents are `"something"` (yes, with
If a user creates a TXT record whose contents are `"something"` (yes, with
double quotes), some APIs get confused.
This bug is most likely to appear in a provider that uses
@ -28,7 +28,7 @@ in your `auditrecords.go` file.
## Step 1: Create the test records
Log into your DNS provider's web UI (portal) and create these 4 TXT records. (Don't use DNSControl!) Yes, include the double-quotes on test 1 and 3!
Log into your DNS provider's web UI (portal) and create these 4 TXT records. (Don't use DNSControl!) Yes, include the double-quotes on test 2 and 3!
| Hostname | TXT |
|---------------|-----------|