In 3.4.2 the HTTP backend removed the priority field. The priority value was the first value in the content string. In 3.4.5 the behaviour has reversed and including the priority in the content string causes an error. I can't find it documented anywhere. Is this intentional behaviour or there a regression issue?
Mark
_______________________________________________ Pdns-dev mailing list Pdns-dev@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-dev
