error resolving yp.shoutcast.com

[summer]

I am running shoutcast on linux. (By the way thanks for the help in fixing the conf problem) I start up shoutcast and everything starts up fine until I get the error
error resolving yp.shoutcast.com
This runs for a while then our broadband connection cuts off. We have several computers connected to the router and only the connection on the computer with shoutcast cuts off. This has happened twice. What does that mean? I have researched forums and google. I see where people mention that this error comes up when there are DNS problems. Maybe a possible wrong firewall setting. We are not running a firewall on our computer, just on our router. However, We don't get the NAT error or whatever it was which says we need to put the firewall down, etc. I am not sure what is going on. Can you help please. Feel like we are so close to getting this going. Someone mentioned installing bind as a fix to this. Not sure what that is and do you recommend it. Thanks again.

[summer]

Hey guys. Any body have an idea about what is going on. Any help would be appreciated.
I am running shoutcast on linux. I start up shoutcast and everything starts up fine until I get the error
error resolving yp.shoutcast.com
This runs for a few minutes then our broadband connection cuts off. We have several computers connected to the router and only the connection on the computer with shoutcast cuts off. This has happened twice. What does that mean?

[sputnik radio]

you have to have the firewall disabled on everything. and you must have ports open . Also with linux check to see that your Iptables are not blocking the ports.

[fc*uk]

can you actually post the output of sc_trans? This may shine some light on what is going on.

[summer]

I have attached sc_serv.log and sc_trans.log. Also have attached sc_serv.conf and sc_trans.conf in case I have something wrong there. The Port is open even though I get the NAK error. Firewall is disabled. Not sure about the iptables. Checked in Suse documentation but couldn't find where to disable them.

[fc*uk]

Well, I do not see too much wrong with your logs and configs besides the nak error (I am guessing that you left the edited the password field so others could not see it).

here is a good giude to IPTables: http://www.siliconvalleyccie.com/linux-hn/iptables-intro.htm

However, if you are behind a router, then I would recomend turning off the linux IPTables as the router's is more than enough...

[summer]

Thanks for all the help and the information was great. We have things going, I think. Just one more step. The shoutcast is playing and gives no error messages. We go into our DNAS webpage at http://127.0.0.1:8000 and it shows shoutcast is running. But when we try to access from the internet, no luck. Our link is 24.75.193.150:8000/listen.pls which is our static IP and port. Is this what we need to have here? In searching the forums I have also seen the link without the listen.pls and tried that but no luck either. Would you please try to access our site and see what you get? I have noticed today that I couldn't get in to shoutcast site. It kept giving me the notice that it had too many users. That shouldn't effect people logging in directly to our link, should it? Thank you for all your help. You guys have been tremendous.

[fc*uk]

well, I got the same results that you did; I could not access the link. As far as the link goes, the listen.pls bit just directly opens winamp from the browser, if you cut listen.pls out people will simply get the dnas web interface that you have seen. So, it does not matter which link you give. Also, the shoutfcast site being busy does not impact people being able to tune into your stream.

The message I got was that the host was taking too long to respond, which may be a little criptic. This could mean that you do not have the bandwidth to support what ever stream you are trying to send out, or a firewall is blocking things.

So, have you opened up ports 8000 and 8001 in your router as well for the 24.75.193.150 IP address? Also, are you sure that you have the bandwidth to support what you are trying to do?