![]() ![]() ![]() |
|
I have the Tripleplay 150. I had been getting DNS errors almost daily when web browsing. Phoned Slingshot. They changed the DNS numbers in router to the Google ones (8.8.8.8 and 8.8.4.4)
So far no more DNS errors. From what I understand they could be more reliable than Slingshots ones.
dukester:
I have the Tripleplay 150. I had been getting DNS errors almost daily when web browsing. Phoned Slingshot. They changed the DNS numbers in router to the Google ones (8.8.8.8 and 8.8.4.4)
So far no more DNS errors. From what I understand they could be more reliable than Slingshots ones.
Yeah, thats what I use too, I think I gave someone that dns as well on here. Slingshot dns was useless and had to keep clearing cache and flushing dns. Other time restart modem.
ONly have oe issue to sort out with them now ... ... will ifnd out today what the result is.
8002F994:
dukester:
I have the Tripleplay 150. I had been getting DNS errors almost daily when web browsing. Phoned Slingshot. They changed the DNS numbers in router to the Google ones (8.8.8.8 and 8.8.4.4)
So far no more DNS errors. From what I understand they could be more reliable than Slingshots ones.
Yeah, thats what I use too, I think I gave someone that dns as well on here. Slingshot dns was useless and had to keep clearing cache and flushing dns. Other time restart modem.
ONly have oe issue to sort out with them now ... ... will ifnd out today what the result is.
Good to see this post as I also was having DNS problems and had to resort to flushing the DNS. Put those new settings into the NF4V and hope for the best.
I believe the following will apply to the TripplePlay as well as my NF4V modem. Two things: One, the phone would cut off after 30 minutes and I would have to phone the number again, or be phoned again by the other party.
What was causing it was that the NF4V was configured by default to cut off the call at just below 1800 seconds. The Slingshot team changed that figure to 7200 and problem is fixed.
Log into the Modem and on the left panel\Voice\SIP Advanced Settings. On the right panel\change "Session Time Expire" to read 7200. Click on 'apply'. All done
Two, By default, the Call Waiting is on. I would be on a call and when someone phoned me, they would not get a busy signal. They would hear the ringing tone until it cut off. I would get a beep and my phone would display the incoming number. All well and good for those who use Call Waiting, not so good for those who don't, like me.
Slingshot had to check if the Call Waiting settings at their end were enabled or not. They weren't, so it was to do with the modem settings.
Go to the same page as number One, on the right panel, at the top, untick the Call Waiting in either Line 1 or 2. It depend which port on the back of the modem you have your phone plugged into. Slingshot got me to click 'Apply".
They then tested by phoning me from another phone of theirs but the Call Waiting was still enabled. You have to go to Management\Reboot and on the right plane, click Reboot. Close the browser page, wait 2 minutes and then Call Waiting should be a distant memory. lol
Hope this helps someone as it can be a long wait on Slingshots 0800 number.
dukester:
I have the Tripleplay 150. I had been getting DNS errors almost daily when web browsing. Phoned Slingshot. They changed the DNS numbers in router to the Google ones (8.8.8.8 and 8.8.4.4)
So far no more DNS errors. From what I understand they could be more reliable than Slingshots ones.
Unless you understand the reasons why it's bad you should never use Google DNS on a permanent basis. While many of the CDN issues are now resolved, it's safe to say your CDN and general internet experience will still not be as good as your ISP's own DNS.
Of course if your ISP can't deliver a working DNS service then maybe it's time to move to another ISP.
sbiddle:
dukester:
I have the Tripleplay 150. I had been getting DNS errors almost daily when web browsing. Phoned Slingshot. They changed the DNS numbers in router to the Google ones (8.8.8.8 and 8.8.4.4)
So far no more DNS errors. From what I understand they could be more reliable than Slingshots ones.
Unless you understand the reasons why it's bad you should never use Google DNS on a permanent basis. While many of the CDN issues are now resolved, it's safe to say your CDN and general internet experience will still not be as good as your ISP's own DNS.
Of course if your ISP can't deliver a working DNS service then maybe it's time to move to another ISP.
I have the date circled that my contract with slingshot is up.
Hey all,
Forgot to come back here and say that we received the modem a day or two after my last post. The modem was sent in a cardboard box with absolutely no packaging as seen here: https://imgur.com/xe6ovGx, so nice one slingshot.
HOWEVER. The internet has not failed once since then, our phone line has not had issues either and the odd intermittent issue of DNS server not being found and websites such as google or trademe going down for a few minutes have occurred. But nothing horrible. Pretty happy with the outcome so far.
Highly recommend this course of action if anyone else has a Tripleplay modem. Shocks me that they still send those modems out!
|
![]() ![]() ![]() |