As ytechie pointed out, custom domains use redirection, not DNS entries. And, the redirection isn't particularly robust. My server sits behind a firewall, and has an RFC1918 address. For some reason, the redirection system thinks that can work:
- Code: Select all
02/19/14 04:45:25 Browsing http://mike_s.subsonic.org
Fetching http://mike_s.subsonic.org/ ...
GET / HTTP/1.1
Host: mike_s.subsonic.org
Connection: close
User-Agent: Sam Spade 1.14
HTTP/1.1 302 Moved Temporarily
Server: Apache-Coyote/1.1
Location: http://192.168.168.1:0/
Content-Language: en-US
Content-Length: 0
Date: Wed, 19 Feb 2014 09:45:25 GMT
Connection: close
I think that's different than how it used to behave, but I haven't tried using it for a long time. I run Subsonic with SSL on a custom port number (DNAT) and as I recall that's always been broken.