Switching servers?

geniegate · 15th May 2012, 16:52

I've decided to try another host, installed shoutcast, the key, etc..

Anyway, for the moment, I have 2 stations on the shoutcast directory.

I've updated DNS, done all that, but now I'm trying to find a way to minimize the
effects of switching, so that the cached IP's and so-forth continue to work.

Whats a good strategy? I'm thinking of bring the old shoutcast server down, setting it to private (or removing the key) and then just letting it run w/out the directory.

Will this cause problems? Will people with the old directory in their cache continue to work? (and will it be updated in such a way that they can find me again when I shut the old one down?)

Thanks!

Jamie

DrO · 17th May 2012, 12:24

if someone has specifically bookmarked / stored a link to the existing server and details change then at that moment it will just die for them and there's not too much which can be done about that.

keeping the existing running with a message to move seems to have been a common way other people do it but that's not ideal either.

the main problem is the reliance upon IP addresses and the v2 DNAS (as you seem to be using) not correctly coping with the destip config option in that it's not passed on / processed by the YP as with that working, you'd then be able to specify a DNS name for the stream and then can move things around without causing clients issues when they have bookmarked things.

that is something i'm working on improving (have in progress) but it's obviously not going to help you at the moment. i guess one other way might be to setup a redirect rule in apache for example on the existing server to try to direct client connections to the new one which does then mean stopping the existing DNAS instance and still may not work if a client doesn't properly handle redirects.

-daz

geniegate · 17th May 2012, 13:02

Thats basically what I did. Kept the old one going, in private mode, until they shut that account down.

That will be really cool when the DNS feature works! :-)

The server I switched to has had some issues too, (none to day, yet..) so I might have to switch servers... again... (and I might not be able to keep the old one going very long, if at all.)

15th May 2012, 16:52	#1
geniegate Junior Member Join Date: May 2008 Posts: 34	Switching servers? I've decided to try another host, installed shoutcast, the key, etc.. Anyway, for the moment, I have 2 stations on the shoutcast directory. I've updated DNS, done all that, but now I'm trying to find a way to minimize the effects of switching, so that the cached IP's and so-forth continue to work. Whats a good strategy? I'm thinking of bring the old shoutcast server down, setting it to private (or removing the key) and then just letting it run w/out the directory. Will this cause problems? Will people with the old directory in their cache continue to work? (and will it be updated in such a way that they can find me again when I shut the old one down?) Thanks! Jamie

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

17th May 2012, 12:24	#2
DrO Join Date: Sep 2003 Posts: 27,873	if someone has specifically bookmarked / stored a link to the existing server and details change then at that moment it will just die for them and there's not too much which can be done about that. keeping the existing running with a message to move seems to have been a common way other people do it but that's not ideal either. the main problem is the reliance upon IP addresses and the v2 DNAS (as you seem to be using) not correctly coping with the destip config option in that it's not passed on / processed by the YP as with that working, you'd then be able to specify a DNS name for the stream and then can move things around without causing clients issues when they have bookmarked things. that is something i'm working on improving (have in progress) but it's obviously not going to help you at the moment. i guess one other way might be to setup a redirect rule in apache for example on the existing server to try to direct client connections to the new one which does then mean stopping the existing DNAS instance and still may not work if a client doesn't properly handle redirects. -daz

17th May 2012, 13:02	#3
geniegate Junior Member Join Date: May 2008 Posts: 34	Thats basically what I did. Kept the old one going, in private mode, until they shut that account down. That will be really cool when the DNS feature works! :-) The server I switched to has had some issues too, (none to day, yet..) so I might have to switch servers... again... (and I might not be able to keep the old one going very long, if at all.)