Vodafone Cable DNS resolution issues

Forums › One New Zealand (including Vodafone, WxC, Farmside) › Vodafone Cable DNS resolution issues

1 | 2 | 3 | 4 | 5 | 6

freitasm

BDFL - Memuneh
79294 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1092191 19-Jul-2014 22:08

citrofia: From what I've read here it looks like these should have been changed sometime ago even if I stayed on the old service.
I obviously missed the memo.

I have been using cable since Chello - which is late 90s. Once SaturnTelstraClear took over Paradise it was .43 and .44... TelstraClear (and now Vodafone) installers are the ones that missed the memo and still go around erroneously pushing the Paradise DNS. The .43 and .44 servers should be all the cable users have to configure.

citrofia

10 posts

Wannabe Geek

#1092204 19-Jul-2014 22:31

freitasm:

I have been using cable since Chello - which is late 90s. Once SaturnTelstraClear took over Paradise it was .43 and .44... TelstraClear (and now Vodafone) installers are the ones that missed the memo and still go around erroneously pushing the Paradise DNS. The .43 and .44 servers should be all the cable users have to configure.

Jeez, in that case you've got to wonder what percentage of TC/VF cable customers are actually set up correctly!?
I mean if VF can find the time and money to send me completely erroneous info about my upgrade to an 'ADSL 500gb package' (no, I think you'll find that was Fast 50 80Gb) and then bill me for Fast 50 Unlimited (no seriously, check the verbal contract, I asked for 80GB), then surely they could suggest that I check my router settings if I'm having any issues?

Anyway, I know my brother has the problem so I'll be checking his router tomorrow.

insane

3240 posts

Uber Geek

ID Verified

Trusted

#1092213 19-Jul-2014 23:11

citrofia:

Jeez, in that case you've got to wonder what percentage of TC/VF cable customers are actually set up correctly!?
I

There's a fair bit of wizardry which they could use behind the scenes to get around that without too much effort if they wanted. To me it sounds like their issues have been related to DNS denial of server attacks, and they've made one change to try stop those. Next they'll need to work on stopping them coming from within their own user base which is a lot more tricky... The ISP I used to work for successfully went through a similar exercise earlier this year, was an enormous pita!

freitasm

BDFL - Memuneh
79294 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1092468 20-Jul-2014 13:48

^^^^

Exactly this

m197

5 posts

Wannabe Geek

#1094602 24-Jul-2014 00:01

I noticed the issue creeping back today, a few pages not loading or partially loading through the afternoon. Back to OpenDNS it is... I'm on unlimited 50 down cable in Wellington.

ghettomaster

387 posts

Ultimate Geek

#1094668 24-Jul-2014 09:06

I've had Cable for years and found the DNS servers 203.97.33.14 and 203.97.37.14 to be very reliable. I'd be curious to see how others fare if they switch to those ones.

ghettomaster

387 posts

Ultimate Geek

#1094670 24-Jul-2014 09:08

Oh - I thought I mentioned those servers before in this thread and I can see now I did. Has anyone given them a go?

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

jimbob79

673 posts

Ultimate Geek

#1094671 24-Jul-2014 09:12

ghettomaster: I've had Cable for years and found the DNS servers 203.97.33.14 and 203.97.37.14 to be very reliable. I'd be curious to see how others fare if they switch to those ones.

These where the original DNS server when I first had TC cable installed in May 2011 and I switch to the recommended VF DNS servers because I was have all kinds of problem with iTunes and iOS app updates.

freitasm

BDFL - Memuneh
79294 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1105111 8-Aug-2014 20:18

That's not the problem. These are the servers to use on Vodafone cable.

zocster

1983 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1136500 24-Sep-2014 13:35

Hi, just curious I am having PITA problems with my office 365 emails on handset, I am on Vodafone via mobile and Vodafone on Cable in Christchurch. In the last 3 days I have had problems setting up/ receiving/ sending emails on wifi.

To ensure that I get my emails I have to do this using my mobile data.

Also setting up BBM etc on wifi would just freeze my device, as cable seems to be having issues accessing BlackBerry ID. Again if I leave it on 3G it is fine!

Any help?

Andy Ghozali Geekzone Member	E: andy@ghozali.ru M: +64 21 395 458 A: Andy's Business Services, 231 High St, Christchurch 8011, NZ
www.andy.mobi

zocster

1983 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1137508 25-Sep-2014 14:11

Update to this, I changed DNS to google's and all is working fine, come on Vodafone, what is going on?

Andy Ghozali Geekzone Member	E: andy@ghozali.ru M: +64 21 395 458 A: Andy's Business Services, 231 High St, Christchurch 8011, NZ
www.andy.mobi

mattbush

784 posts

Ultimate Geek
Inactive user

#1137743 25-Sep-2014 18:51

zocster: Update to this, I changed DNS to google's and all is working fine, come on Vodafone, what is going on?

Most of us have given up on this issue

stevenj

2 posts

Wannabe Geek

#1144940 1-Oct-2014 16:34

This has been getting worse and worse for me. I am now seeing quite frequent DNS resolution failures, several a night easily. The strange things is I run my own Bind server which does not now forward to vodafone's DNS servers, yet performance still sucks. I am left wondering if they are transparently proxying DNS requests to their DNS servers? I cant see what else can cause/explain such bad performance.

Yabanize

2350 posts

Uber Geek

#1144959 1-Oct-2014 17:16

I get this alot too, a refresh usually fixes it though..

stevenj

2 posts

Wannabe Geek

#1145408 2-Oct-2014 10:16

Not in my case, or its got to the stage that the outage/loss is longer that the refresh time just happened to be, ie I am talking minutes not seconds.

1 | 2 | 3 | 4 | 5 | 6