Re: semicolons in dig output

2016-11-09 Thread Matthew Pounsett
On Fri, Nov 4, 2016 at 13:51 Robert Edmonds wrote: > Matthew Pounsett wrote: > > Was this actually a change between BIND 9.8 and 9.9? Was it deliberate, > or > > an accident that might be reversed at some point? > > It's this change: > > 3953. [bug] Don't escape semi-colon in TXT

Re: semicolons in dig output

2016-11-04 Thread Robert Edmonds
Matthew Pounsett wrote: > Was this actually a change between BIND 9.8 and 9.9? Was it deliberate, or > an accident that might be reversed at some point? It's this change: 3953. [bug] Don't escape semi-colon in TXT fields. [RT #37159] The corresponding git commit is here: https:

semicolons in dig output

2016-11-04 Thread Matthew Pounsett
I had a question from a one of our developers today about semicolons in TXT records. It seems he and someone he's working with were getting different output from dig when querying for TXT records that contained semi-colons. One person saw them escaped, the other didn't. It caused some confusion b