Possible someone is using my authhash?

[SomeJ]

I have been having complaints that our "listen" playlist that is auto generated by our v2 server has links that takes the listener to another station.

Did some digging today and sure enough, my root relay server some how has it's client playlist polluted and takes the listener somewhere else.

I upgraded to 2.4.2 and the problem persists.
Even the client playlist that can be downloaded from the shoutcast.com website has the bad servers.
http://yp.shoutcast.com/sbin/tunein-...n.pls?id=47475

As of right now, there are 2 servers listing for "audioplayerz dot com". Normally I would not make a huge deal of it, but they are very high up on the list so if someone fails over off our root server they will roll over to one of these others.

I am not real sure what could cause this unless somehow someone is using our auth hash, so their servers and ours keep getting mixed together when the client playlists are generated?

Any advice or help would be greatly appreciated.

Thanks,
Jason

[DrO]

i've removed the incorrect ones though will need to keep an eye on things. as you're running a combination of 1.x and 2.x DNAS and due to the 1.x DNAS in your listing, those have led to being hit by the 1.x clustering issue.

only real way to avoid it is to use all 2.x for all instances of the stream as we've got things in place which tries to help 1.x and 2.x DNAS clustering work automatically but trying to reliably do clustering in the listings for 1.x DNAS when you cannot be 100% certain of it (since there's no piece of reference data to use, unlike with 2.x where you've got the authhash value) and so it has to do what it can based on the information from the 1.x DNAS.

[SomeJ]

Awesome! Thanks DrO!! Looks like the client playlist is behaving properly now.

I will see what I can do about getting the v1 servers shut down.

Thanks and hope you have a great weekend!!
Jason