I am in the process of upgrading the desec provider and ran into a snag when I tried to implement support for HTTP records. The biggest problem I have is that I don't really know how to deconstruct the query name into the different pieces of a ServiceBinding. That is, parsing the name and then understanding what piece of the name represents the port and what represents the name is not trivial. I think I am going to work around this by returning a wrapped RR type for now.

Also, I think it's confusing that when getting a record for "_1234._https.foo.bar" ends up returning a record with a different name.