Finally, we got rid of this error with the FTL v5.18 update!
I had this error in the FTL.log for a very very long time, it did not cause any problems but just filling in the log file. Now with the FTL v5.18 update, which updated dnsmasq v2.87RC1, it is fixed.