Main Board Index Forum Index

Device: AudioTron Forum:   Device: AudioTron

Topic: Radio server not working?

August 4, 2020, 12:33 pm #1
Quote:
Hi,

The Audiotrons try to connect to duncan.turtleradio.com
Turtlebeach forwarded that subdomain to our IP address until a few years ago.
Now the duncan subdomain is dead. Our IP address is: 62.251.124.128


Crystal clear. Thank you!
August 4, 2020, 9:42 am #2
Hi,

The Audiotrons try to connect to duncan.turtleradio.com
Turtlebeach forwarded that subdomain to our IP address until a few years ago.
Now the duncan subdomain is dead. Our IP address is: 62.251.124.128


August 3, 2020, 7:50 am #3
Quote:
Hi,

No, nothing changed as far as I know.. 
I host multiple websites hosted on this IP. None of them have issues.
Please check again and let me know if the problem persists.

~William





(Last Edited by penbex on April 3, 2020, 10:32 pm)

What are the correct setting for DNS resolution for Audiotron to work with either listenlive.nl or duncan.turtleradio.com, or turtleradio.com or  ??? 

Please help!
Zzeonblue
August 3, 2020, 6:30 am #4
Hello, does anyone have an audiotron that plays the internet radio using either the 62.251.124.128 or the
 62.251.119.103 addresses? 

If you do have Audiotron, could you point me to an updated software (rom-like) or individual setup programs for the last release, I am running the last firmware they released 3.2.25.

Thanks,  Zzeonblue
July 19, 2020, 7:40 am #5
Indeed it is i did a bit of fiddling rebooting and resetting also refreshed the device and favourites on the website the Audiotron will not pick up directly on 62.251.124.128,
so set it up to Dnsmasque to the old 62.251.119.103 and it sprung into life hope this helps others,
July 13, 2020, 7:18 pm #6
I have tried to add the new server address but does not work dnsmasque or normal connection to internet with my username even refreshed the list on this site was working only last week on the old server IP 
July 11, 2020, 9:32 am #7

The server is on 62.251.124.128 since July 2019.
All is up and running.

July 11, 2020, 8:45 am #8
Hi all 
Im using the Atron AT 100 and dnsmasque was running fine on 62.251.119.103 but has stopped only in the last few days im getting slightly confused do i dnsmasque it to 62.251.124.128 or something different,

thanks.
May 10, 2020, 5:27 pm #9
1. Can we submit lists of our own which would match up against our (inherent) Turtle Radio IDs ?  If yes, is there a process I can be pointed to?  If not, that's fine!

You can have your own list on here - with an id of your choice. But it then becomes the only list that you have,.
My recollection is that with the official TB version you could have your own list plus access the shared one.
But not here - it was a bit too complicated to do at the start when it was not clear how many users thee would be ... and I suspect that has not changed much since.


2. What is process for submitting updates to the 1,000 that are on the list?  There is a station I really like that has a new streaming location... You get the idea.
Post in the general area in the forum - since I think the 1,000 list is a subset of the overall list and hopefully a changed URL that you find would benefit listeners who use other devices that have access to the full list.


3. Is the limit still present for Shoutcast and Icecast?  I am guessing it is but wanted to at least ask...
There is no transcoding (etc) done from this site - your Audiotron is accessing the stream URL directly. So it is still limited to whatever was possible before.


4. Is the 1,000 stations a hard limit?
Not really - but the fear was that making it too big would crash the device through lack of memory.

May 9, 2020, 2:33 am #10
Hello everyone,

I am a new member who has been around the block with a few Audiotrons over the last decade. I spent some time trying to get a local SMB (share) working on my router but found they do not support "anonymous" as a user-type...  Then I read about this service and thought I would give it a try.  Thank you for being here!

I found the DNS change to config on my router and can now pick up 1,000 stations. I set a few as favorites and I am good-to-go.  I do have a few questions for anyone willing to respond.

1. Can we submit lists of our own which would match up against our (inherent) Turtle Radio IDs ?  If yes, is there a process I can be pointed to?  If not, that's fine!

2. What is process for submitting updates to the 1,000 that are on the list?  There is a station I really like that has a new streaming location... You get the idea.

3. Is the limit still present for Shoutcast and Icecast?  I am guessing it is but wanted to at least ask...

4. Is the 1,000 stations a hard limit?

That's good for now.  Again, thank you all for pulling this together!!
April 5, 2020, 12:33 am #11

I serve up a local DNS domain and for some reason your web server was not happy recently.  I just re-tested and it pulled 1,000 stations from your server.  (I just need to fix/update the station I listen to).


April 4, 2020, 8:49 pm #12
Not sure why my DNSmasq stop working but after a few reboots and some playing around I got it back up and working. Thanks for keep this going.

Tim


April 3, 2020, 10:27 pm #13
Hi,

No, nothing changed as far as I know.. 
I host multiple websites hosted on this IP. None of them have issues.
Please check again and let me know if the problem persists.

~William





(Last Edited by penbex on April 3, 2020, 10:32 pm)
April 3, 2020, 8:10 pm #14
Did the IP address for the list change from 62.251.124.128. I am no longer able to redirect to it using DNSMASQ. It worked great yesterday.

Thanks 
Tim
September 14, 2019, 4:38 pm #15

I can confirm that I've updated my internally hosted DNS to point at 62.251.124.128  and I can breathe again.

I really think it is dumb for TurtleRadio to not bother hosting that DNS A record.  Such a tiny little technical edit.  They must have some really short-sighted IT folks.


September 10, 2019, 3:48 pm #16
Hey,

even with DNS rerouting duncan.turtleradio.com to the new IP-Address 62.251.124.128  my Audiotron can't connect to the Radio-Server. It used to work with the IP Address that was used before.
Anyone else having this Problem? Or is there Anything I miss with the new Address? Maybe some subfolder I have to name? 
August 2, 2019, 5:53 pm #17
I am not a networking expert. can't we ask Google Public DNS or OpenDNS, etc to redirect to the correct working address?
if all fails use the two files below to get the radio station list localy.
List in text format
https://drive.google.com/open?id=1PiCvW1ELbsbeALdDAJE-UoagIXinyjCV

Editor in Excel format
https://drive.google.com/open?id=1XYvk3fRlQ1GXbsNHVWVBnVZggaVYZUhB

(Last Edited by hiran on December 11, 2019, 3:01 am)
May 22, 2019, 7:23 pm #18
m3repairs hint works also on RouterOS Devices.

For that you have to make a static DNS-Entry

Log in to Interface, klick IP>DNS>Static And "Add New". 
Here, check the "enabled" Checkmark. 
Under "Name" put "duncan.turtleradio.com"
Leave Regexp empty
Under "Adress" put "62.251.119.103"
Leave TTL as it is or adjust to your liking.
Klick Apply

Now set the RouterOS Device as the DNS for your Audiotron, via the Audiotron Webinterface, if it isn't already.
Webradio should work now on the Audiotron. 


Also, If your Router does not support any DNS rerouting, paulwebster has made a Tutorial for using a Windows-Machine as a DNS, for rerouting:


(Third Post)

May 22, 2019, 12:06 am #19
I did this on my FIOS and it works a charm!
Under "Advanced-DNS"  on the router I added this entry:
Host Name-duncan.turtleradio.com IP Address-62.251.119.103
Easy.





(Last Edited by 51JVS23 on May 22, 2019, 10:48 am)
(Last Edited by 51JVS23 on May 22, 2019, 10:53 am)
March 29, 2019, 9:37 pm #20
I cannot thank you enough m3repair I had an old DIR-615 router with DD-WRT installed its probably 10 years old so I reset it and fired it onto the network done your workaround and its now playing my Fav list from the site absolutely amazing work my audiotrons live again,

March 25, 2019, 1:35 am #21
Hello everyone sorry for the delay in getting back to you, as of this evening I do have my own Audiotron's working again, and as I type this I am listening to one of them   Hopefully some of you are familiar with using DD-WRT on routers, but essentially I logged into my router with the custom firmware of course. I went to the services tab, scroll down to DNSMasq and make sure it is selected as Enable, then scroll down a bit to Additional DNSMasq Options type in the command as follows   address=/duncan.turtleradio.com/62.251.119.103    What this essentially does it the router intercepts any requests to the duncan.turtleradio.com URL and sends them to 62.251.119.103 instead of the old 213.124.89.2

What I need to know is how do you want me to explain this in more detail to others? Shall I make a video about this perhaps? (not certain how technical everyone on this forum is)

I found a link which may help others but obviously you will be inputting the address shown above in my post as opposed to what they show in there tutorial, here is the link if it helps someone who needs to see it a bit better. https://www.instructables.com/id/URL-Redirect-Prank-using-dd-wrt/

March 17, 2019, 9:07 pm #22
I would like to know how you get on with that and if a workaround could be achieved to listen to any internet stations my local list file will no longer pickup any stations but I guess that was pointed at the same IP address but not sure.
March 16, 2019, 7:50 pm #23
My emails so far have achieved the same result, I even offered to pay or pay a portion to the change made. I even suggested if we can purchase the domain in question. But sadly to no avail. Looking into redirecting my router to intercept the url and redirect it to the correct ip. Haven't tested it yet though. 
March 15, 2019, 3:00 pm #24
Let’s hope that someone will be able to help it’s a real shame if it can no longer be used for internet radio
March 15, 2019, 11:13 am #25
I have exchanged a few emails with them and they continue to say that they will not make the change.
I have tried numerous approaches with different suggestions.
An issue for them is that they outsource the management of their DNS and it costs them money to make a change.
I have offered to pay them to help solve the problem.

I am now looking for TB staff/ex-staff who might be able to help.
March 12, 2019, 9:48 am #26
This morning I had this email from Turtle Beach I guess they are not going to help such a shame , Dear Nick, Thank you for your interest in our legacy product. Unfortunately we are unable to accommodate any request related to the AudioTron or the old "Turtle Radio" service. The Audiotron was a Turtle Beach product from 2001 to 2004. We had stopped production of this product 15 years ago, and we no longer support it. DNS management of the URL comes with an annual cost to Turtle Beach, and redirection would also incur support and assistance with further diagnostics, troubleshooting or other analysis that may arise. In addition, we cannot redirect a Turtle Beach-owned URL to a site over which we have no control. We apologize for any inconvenience this may cause you. Sincerely, The Turtle Beach Support Team
March 6, 2019, 11:26 am #27
Thanks for the info I will send this to them and try to get it resolved,

March 6, 2019, 9:56 am #28
Quote:
 I'm afraid there is no-one left here who has access to programming or any development tools for the Audiotron products. The product is obsolete and is no longer supported. I'm sorry we can't help. Sincerely, Rowan

Yeah, it seems the person who replied thought you wanted changes to the Audiotron firmware. 
But that is not the case. There is no programming/development or anything like that involved.

After the Audiotrons went obsolete, Turtlebeach was so generous to change the DNS entry for "duncan.turtleradio.com" and point it to our server.
By doing that, Turtlebeach offered extended support to the obsolete Audiotrons which is of course very nice. 
A few years ago our IP address changed and they also did an update to the DNS records. 

Right now the DNS record looks like this:
host: duncan.turtleradio.com, class: IN, ttl: 3600, type: A, ip: 213.124.89.2
In order to have the Audiotrons find the server again it should be updated to read:
host: duncan.turtleradio.com, class: IN, ttl: 3600, type: A, ip: 62.251.119.103

Changing the IP address on the DNS entry is a very simple task however, it does require some knowledge on how to do this and it requires sufficient admin rights to make the changes to the DNS records.
Alternatively to the above IP change there is also a way to make the DNS redirection based on a domain name (listenlive.nl). 
If they would use the name based redirection it would keep on working even when the server IP address changes.

If you want you can send them the above information as well.




(Last Edited by penbex on March 6, 2019, 9:57 am)
March 6, 2019, 2:26 am #29
I also went ahead and sent an email request basically stating the same info. Hopefully we have success. 
March 5, 2019, 6:36 pm #30
Probably not the answer I was looking for from Turtlebeach Hi Nick, I'm afraid there is no-one left here who has access to programming or any development tools for the Audiotron products. The product is obsolete and is no longer supported. I'm sorry we can't help. Sincerely, Rowan
March 5, 2019, 10:40 am #31
I have Emailed there support Support@turtlebeach.com,

lets see if we can get this changed,

Hi Turtlebeach Support,

 

I am a user of the Audiotron AT-100 and have two units which work perfectly all these years on its an amazing piece of kit and I appreciate that you no longer support them however being a member of the listenlive.nl forum and using there workaround which has supported these units for many years have updated there server and now your DNS Entry does not match,

Would it be at all possible if you could alter your DNS entry from the old IP (213.124.89.2) to there new IP (62.251.119.103) to match so that the many owners and users of this excellent piece of kit can once again listen to internet radio,

I appreciate that you do not have to do this but it would be a nice gesture to all us old Audiotron users and listenlive.nl,

 

Kind Regards,

 

Nick Bellamy, UK.

 

 

March 5, 2019, 9:56 am #32
Hi,
Thanks for the info I would also like to contact them see if something can be done about this as it is such a good service from you guys keeping it alive all these years i dont have many other options now as the local list file no longer works if we all get together and mail Turtlebeach maybe they will alter the DNS entry,
March 4, 2019, 11:12 pm #33
how would you like us to get in contact with them ? do you have an email that we could send a message to?
March 4, 2019, 5:02 pm #34
Below a message from Paul that he posted yesterday to the Audiotron group.
Best thing would be if Audiotron users ask Turtlebeach support very kindly if they could make the DNS change from the old IP (213.124.89.2) to our new IP (62.251.119.103) address.


---
I’ve had feedback from TB support to say that they will not be changing their DNS entry.
I hope that this is a temporary issue while they work out how easy it is to do and have asked them for more info.

Perhaps if other Audiotron users who were using our workaround via listenlive could also get in touch with them it might help.

They are, of course, under no obligation but it would be a very easy thing to do which, once done, costs them nothing for things to keep a few Audiotron devices working like they were intended to.

Paul Webster 

---

__._,_.___



March 3, 2019, 10:54 pm #35
Is there any update on a fix for the Audiotron yet ?
February 28, 2019, 1:12 am #36
Is the redirect just not happening to the server as I noticed no ping response from it. 
February 26, 2019, 10:57 pm #37
Is it?

February 24, 2019, 6:48 pm #38
Disregard this comment, must have been seeing things, didn't have my glasses on please excuse me 
(Last Edited by m3repair on February 28, 2019, 1:11 am)
February 24, 2019, 6:39 pm #39
yes please do let us know whats happening and when we are back and operational. Thank you dearly 
February 15, 2019, 7:36 pm #40
Thanks for the update I hope its fixed soon please could you post an update when you are back on air,

February 14, 2019, 6:58 pm #41
We hope to have it fixed soon..
February 6, 2019, 4:59 am #42
I haven't been able to access the radio station server from the Audiotron for about a week, presumably due to the server changes on 1/31 mentioned in the update. But it still doesn't work. It worked fine before, and I haven't changed anything, so... what happened??

Main Board Index Forum Index
 
 

Get notified of new forum posts via