Subsonic Forum

I wanted to know if it's possible to have a custom domain url so my Subsonic address turns to a "mysite.com"

can I use 1&1.com for this?

Is Subsonic ever going to have this has an option?

Thank you

dannymumbles

It is possible since I know there is a thread in the forum that describes the subsonic.org/demo server that is hosted on godaddy, not sure if that will help you or not though.

Well I know godaddy can host but I'm not trying to pay for online space and bandwidth use charge... I just wanna be able to havemy own custom domain name.

If you are running subsonic on Port 80, then you can easily have a custom domain name... Just go add the appropriate records to the DNS servers hosting your domain, and it will work fine.

For example, if you own "example.com" and want "subsonic.example.com" to point to your subsonic server, then add an A record to your DNS with the address of your subsonic server and the name "subsonic".

If you are not serving subsonic on port 80, it is a little more difficult. You have to know how to set up a web server that will answer back with a "302" message when prompted that redirects to your real subsonic address and port. Continuing the above example, if you want "subsonic.example.com" to redirect to your real subsonic server at 65.66.67.68:4040, then you would have to have the A record above point to a web server you have control of, and would have to set that web server up to answer to the Host Header "subsonic.example.com" and feed back a 302 redirect to http://65.66.67.68:4040/login.view.

I can help you with specifics in Windows using IIS or apache if you want help setting it up. But your ISP needs to allow inbound port 80 traffic for it to work correctly.

HTH,

Glenn

bushman4 have explained the process eloquently. I use a very similar method, but i host subsonic myself at home. My routers Upnp is useless and i found my xxx.subsonic.org domain not always forwarding due to my router. I had a domain already hosted with bluehost.com for other purposes so i just created a subdomain called: media.mydomain.com and setup an A record as described above to point to my external ip address(i lease a static ip address already). I then opened port 4040 to forward to my ubuntu subsonic server's internal ip address and it is all working flawlessly.

If you don't have a static external ip address, you can overcome that by using something like dyndns.org or similar.

I don't have an experience with 1&1, but Bluehost.com have an excellent control panel that is very powerful and gives you full control over your domain and i would recommend them to anyone.

If you are not serving subsonic on port 80, it is a little more difficult. You have to know how to set up a web server that will answer back with a "302" message when prompted that redirects to your real subsonic address and port. Continuing the above example, if you want "subsonic.example.com" to redirect to your real subsonic server at 65.66.67.68:4040, then you would have to have the A record above point to a web server you have control of, and would have to set that web server up to answer to the Host Header "subsonic.example.com" and feed back a 302 redirect to http://65.66.67.68:4040/login.view.

I'm having trouble figuring this out. I have a web server/domain but I don't understand how to edit my A record (is that a configuration with the domain registrar?) or how to setup the response to header information with 302 redirect. Do you have any good sources that I can reference in order to learn this?

With 1&1 you:

1. Go to the 1and1.com and sign in.

2. Click domains

3. Click the check-mark next to the domain you wish to use for subsonic.

4. Then along the top of the domains there is a DNS drop-down & select edit DNS

5. Scroll down to where it says "IP Address (A-Record) :" and change it from 1&1 IP Address to Other IP Address

6. It will then load a section of 4 text-boxes to input your public ip address where your server is located.

7. Select OK and give it a few minutes for the dns records to update and you should be good to go.

This will work for http or https. No need to specify the port in the dns record as it always looks for port 80 and 443.