Re: semicolons in dig output
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 fields. [RT > #37159] > > The corresponding git commit is here: > > > https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=9a36fb86f5019f25705d25ea729d03fcf8ecaa95 > > -- > Robert Edmonds > Thanks for the pointer! ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: semicolons in dig output
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://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=9a36fb86f5019f25705d25ea729d03fcf8ecaa95 -- Robert Edmonds ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
semicolons in dig output
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 because they weren't sure what was actually in the data. As far as I can tell, it looks like dig's behaviour changed somewhere between 9.8 and 9.9. In later versions semicolons in quoted text aren't escaped. I see several posts from the archives about people being surprised by the escaping, but nothing that indicates anyone at ISC thought it was a bug. I also haven't (yet?) found any release notes about the change in behaviour. 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? Thanks! ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
