Scannercast Issue

[johnmac]

I am running the latest version of scannercast (Full Edition) and am having problems connecting to RR.

I have been using this setup for many months with no problem.

I get the following error message - "Cannot resolve api.radioreference.com"

Any suggestions on what I should look at to resolve the problem.

 

[GordonE]

Try rebooting your computer and see if that helps.

If it doesn't, if you go to RadioReference.com API/Integration do you see "Welcome to api.radioreference.com"?

-- Gordon

 

[datainmotion]

I am running the latest version of scannercast (Full Edition) and am having problems connecting to RR.

I have been using this setup for many months with no problem.

I get the following error message - "Cannot resolve api.radioreference.com"

Any suggestions on what I should look at to resolve the problem.

I'll volunteer the dumb question (if Gordon's solution doesn't resolve it) - right before you noticed this, did you install any software or did MS do an update on your feed PC?

 

[johnmac]

It appears that I have a sound card issue. Could that cause it not to resolve to API.radio reference.com

I was able to get the API welcome message as suggested by Gordon.

I am not able to get to the recording tab on my sound card. It is grated out under advanced controls. Have rebotted numerous times, with no luck.

 

[GordonE]

It appears that I have a sound card issue. Could that cause it not to resolve to API.radio reference.com

Nope, the "Unable to resolve api.bbscanner.com" error message would be completely unrelated to a sound card problem. This error means that when ScannerCast asked your computer to convert api.bbscanner.com into an IP address, your computer was unable to. When ScannerCast asked your computer to perform the conversion it would have asked your router or your Internet Provider's DNS server to perform the lookup, the fact that the error was reported means that the lookup failed. This failure wouldn't be on RadioReference.com's side.

I was able to get the API welcome message as suggested by Gordon.

The DNS problem (conversion of api.radioreference.com to an IP address) could have been a temporary one.