Does emby want to know it's own AAAA record or is it the OS?

[pryoclastic 6]

I ran a tcpdump overnight and noticed that emby did a query for it's AAAA record.  I dont have an AAAA in DNS so it failed, but what is odd is that even though the initial request was fully qualified emby ignored the results, appended the DNS suffix of the server and tried again:

 

03:20:56.812989 IP 10.4_._2.31.36215 > 10.4_._2.20.53: 52699+ AAAA? emby.r_.com.r_.com. (42)
03:20:56.812992 IP 10.4_._2.31.47177 > 10.4_._2.20.53: 92+ AAAA? emby.r_.com.r_.com. (42)
03:20:56.813251 IP 10.4_._2.20.53 > 10.4_._2.31.36215: 52699 NXDomain* 0/1/0 (103)
03:20:56.813264 IP 10.4_._2.20.53 > 10.4_._2.31.47177: 92 NXDomain* 0/1/0 (103)

 

What I have not taken the time to figure out is if the query was generated by the OS or by emby.  If it is emby, it feels like a bug since the DNS search suffix should only be applied if the initial query was unqualified.

[Luke 37274]

All we're doing is trying to send http requests to our domains when needed.