YP Problem. Server not Public

[miamigo]

Our stations are also missing from the directory, but are fine on the Shoutcast D.N.A.S. administrator page which is showing the last 10 items played and that the station is online and how many are listening (via our webpage), if you click on the listen tag it sends the info to the player fine but nothing is found in the Directory.

So strange and frustrating,

Paul

[bored_womble]

just something I picked up from a conversation yesterday it appears the YP2 will bascially not allow stations to go into the directory without pre-registration.

It can be seen in some of the error message, http://a.b.c.d/ not registered please wait etc, that this is/has been implemented.

I do not know if this is just for Sc_Serv2, however I suspect this may be a legal way to remove stations from the directory and distance themselves from liability etc.

BW

[Waves216]

My Error message on the logs have changed overnight. Now the logs on the relays are getting this:

<06/11/10@15:02:37> [yp_add] yp.shoutcast.com gave error (nak)
<06/11/10@15:02:37> [yp_add] yp.shoutcast.com gave extended error (Relay url could not register. Try by making primary source public or wait till primary registers.)


I've made the primary server temporarily public to see what happens. So far the server has not said its made a connection to the YP



How do we register the stations to get us back on the YP?

[SoLoRiZe]

Hi

Ive also been getting the following similar error on both my
shoutcast streams for almost a week now and my station
has stop being listed on shoutcast.

<06/12/10@11:08:24> [yp_add] error connecting to yp.shoutcast.com
<06/12/10@11:08:48> [yp_add] error connecting to yp.shoutcast.com
<06/12/10@11:09:12> [yp_add] error connecting to yp.shoutcast.com
<06/12/10@11:09:36> [yp_add] error connecting to yp.shoutcast.com
<06/12/10@11:10:00> [yp_add] error connecting to yp.shoutcast.com
<06/12/10@11:10:24> [yp_add] error connecting to yp.shoutcast.com


I have checked that it was not my firewall, but everything was fine there.
I also checked that I had a tick in the "Make this server public" which there was.

After reading a few other threads I see that other people are suffering
similar errors, but what I cant understand is why is it only effecting some
stations and not others which are currently still being listed?

Does anyone know when this problem is likely to be fixed?
If anyone can shed any light on this or let me know if there is a work
around to get back to being listed, I would be greatful.

Mark