Azure DNS provider cannot deal with unescaped semicolons

I originally commented on https://github.com/github/octodns/issues/79 but it’s probably best to open a new issue.

I’m trying use octodns with Route 53 and Azure DNS.

In Azure, a TXT record with escaped semi-colons yields TWO backslashes via dig.

A TXT record without any escaping yields NO backslashes in the response from dig.

A TXT records surrounded in double quotes … well, it’s just weird, see below.

Unescaped semi-colons:

lsilverman@mgmt-lsilver:~$ dig +short TXT unescaped.trackabout.com @ns1-03.azure-dns.com.
"v=DKIM; k=rsa; p=1234567890"

Escaped semi-colons

lsilverman@mgmt-lsilver:~$ dig +short TXT escaped.trackabout.com @ns1-03.azure-dns.com.
"v=DKIM\\; k=rsa\\; p=1234567890"

Quoted TXT

lsilverman@mgmt-lsilver:~$ dig +short TXT quoted.trackabout.com @ns1-03.azure-dns.com.
"\"v=DKIM; k=rsa; p=1234567890\""

This is causing problems with the sync. Octo is refusing to read the TXT records from Azure due to the missing backslashes. But if I add backslashes, the records are invalid. Catch-22.

[silverl]

@h-hwang Would you be able to update the dependencies for the Azure provider?

I gave it the college try. I’m not facile with Python. I forked and checked out the code base and attempted to bootstrap. I was met with dependency issues between botocore and python-dateutil.

I optimistically upgraded botocore to the latest 1.10.4 but received the same bootstrap warnings.

botocore 1.10.4 has requirement python-dateutil<2.7.0,>=2.1, but you'll have python-dateutil 2.7.2 which is incompatible.

I found this PR which may be related: https://github.com/boto/botocore/pull/1433

[ross]

Isn’t this fixed with #272 ?

I believe so. Closing. Please reopen if not.