TXT record testing
We recently discovered a strange bug 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.
The problem relates to TXT records that have a string with quotes in them.
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
models/t_parse.go) to create TXT records. That function assumes the string should always have the quotes stripped, though it is more likely that the string should be taken verbatim.
To complete this test, you will need a test domain that you can add records to. It won't be modified otherwise.
This bug has to do with double-quotes at the start and end of TXT records. If your provider doesn't permit double-quotes in TXT records (you'd be surprised!) you don't have to worry about this bug because those records are banned in your
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!
Now in your
dnsconfig.jsfile, add these records to the domain:
When you do a
dnscontrol preview, you should see changes for t1 and t2.
#1: MODIFY TXT t1.example.com: ("test1" ttl=1) -> ("\"test1\"" ttl=1)
#2: MODIFY TXT t2.example.com: ("\"test2\"" ttl=1) -> ("test2" ttl=1)
Let's assume you DO see the changes. Push them using
dnscontrol pushthen check the webui to see that the changes are correct.
#1: MODIFY TXT t1.stackoverflow.help: ("test1" ttl=1) -> ("\"test1\"" ttl=1)
#2: MODIFY TXT t2.stackoverflow.help: ("\"test2\"" ttl=1) -> ("test2" ttl=1)
Refresh your provider's web UI and you should see the changes as expected: t1 should have double-quotes and t2 shouldn't. If the change wasn't correctly done, that's a bug.
Remove the lines from
dnscontrol pushto clean up.