This update for pdns fixes the following issue:
Security issue fixed:
{ "binaries": [ { "pdns-backend-remote": "4.1.2-bp150.2.6.1", "pdns-backend-geoip": "4.1.2-bp150.2.6.1", "pdns": "4.1.2-bp150.2.6.1", "pdns-backend-ldap": "4.1.2-bp150.2.6.1", "pdns-backend-mysql": "4.1.2-bp150.2.6.1", "pdns-backend-godbc": "4.1.2-bp150.2.6.1", "pdns-backend-mydns": "4.1.2-bp150.2.6.1", "pdns-backend-lua": "4.1.2-bp150.2.6.1", "pdns-backend-sqlite3": "4.1.2-bp150.2.6.1", "pdns-backend-postgresql": "4.1.2-bp150.2.6.1" } ] }
{ "binaries": [ { "pdns-backend-remote": "4.1.2-bp150.2.6.1", "pdns-backend-geoip": "4.1.2-bp150.2.6.1", "pdns": "4.1.2-bp150.2.6.1", "pdns-backend-ldap": "4.1.2-bp150.2.6.1", "pdns-backend-mysql": "4.1.2-bp150.2.6.1", "pdns-backend-godbc": "4.1.2-bp150.2.6.1", "pdns-backend-mydns": "4.1.2-bp150.2.6.1", "pdns-backend-lua": "4.1.2-bp150.2.6.1", "pdns-backend-sqlite3": "4.1.2-bp150.2.6.1", "pdns-backend-postgresql": "4.1.2-bp150.2.6.1" } ] }
{ "binaries": [ { "pdns-backend-remote": "4.1.2-bp150.2.6.1", "pdns-backend-geoip": "4.1.2-bp150.2.6.1", "pdns": "4.1.2-bp150.2.6.1", "pdns-backend-ldap": "4.1.2-bp150.2.6.1", "pdns-backend-mysql": "4.1.2-bp150.2.6.1", "pdns-backend-godbc": "4.1.2-bp150.2.6.1", "pdns-backend-mydns": "4.1.2-bp150.2.6.1", "pdns-backend-lua": "4.1.2-bp150.2.6.1", "pdns-backend-sqlite3": "4.1.2-bp150.2.6.1", "pdns-backend-postgresql": "4.1.2-bp150.2.6.1" } ] }