From Littlesnitch help:
That's how you get what appears to be the "wrong" hostname for a connection.
I don't believe there's any way around this, as Littlesnitch works on IP addresses not hostnames. If one name is blocked, all names that lead to that IP address will also be blocked.
Little Snitch wants to show the hostname recently entered by the user or used by a process, not the reverse lookup name returned by the Domain Name System (DNS) because the reverse lookup name is often very cryptic. It therefore watches all DNS requests and responses on UDP and TCP ports 53 and 5353, and remembers the names which led to a particular IP address.
If there are multiple names which resolve to a given address, it guesses the “best” name (usually the last one used) to present to the user. In the Connection Alert and in Little Snitch Network Monitor’s connection list, you can view the other names by clicking the hostname.
That's how you get what appears to be the "wrong" hostname for a connection.
xxloader wrote:This also causes connections to be blocked by mistake if one host name is blocked and a different host name with the same IP is supposed to be allowed.
I don't believe there's any way around this, as Littlesnitch works on IP addresses not hostnames. If one name is blocked, all names that lead to that IP address will also be blocked.