Vodafone Cable DNS issues

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

shrub

769 posts

Ultimate Geek

ID Verified

#195770 3-May-2016 12:51

Lately ive been having constant issues with the DNS server. Am I using the standard ones?

DNS Server:

203.97.78.43 , 203.97.78.44

I keep getting this message when opening websites

This site can’t be reached

The webpage at http://www.nrl.com/ might be temporarily down or it may have moved permanently to a new web address.

Search Google for nrl

ERR_NAME_RESOLUTION_FAILED

And if i tracert i get this message

C:\Users\****>tracert www.nrl.com
Unable to resolve target system name www.nrl.com.

I can ping the site.

C:\Users\****>ping 202.148.153.145

Pinging 202.148.153.145 with 32 bytes of data:
Reply from 202.148.153.145: bytes=32 time=66ms TTL=237
Reply from 202.148.153.145: bytes=32 time=67ms TTL=237
Reply from 202.148.153.145: bytes=32 time=62ms TTL=237
Reply from 202.148.153.145: bytes=32 time=62ms TTL=237

Ping statistics for 202.148.153.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 67ms, Average = 64ms

Now here is where it gets interesting if I connect to any VPN server via PureVPN I can access everything again

C:\Users\****>tracert www.nrl.com

Tracing route to www.nrl.com [202.148.153.145]
over a maximum of 30 hops:

1 48 ms 47 ms 48 ms 43.226.229.130
2 46 ms 48 ms 48 ms gi1-15.sw-9-10.as45671.net.au [221.121.151.156]
3 46 ms 49 ms 49 ms vl1208.core-sw-9-1.as45671.net.au [103.13.102.18]
4 46 ms 56 ms 47 ms vl2907.sw-1-1.as45671.net.au [221.121.137.20]
5 49 ms 48 ms 57 ms ve1018.br-9-1.as45671.net.au [203.26.198.62]
6 56 ms 49 ms 50 ms 175.45.124.230
7 64 ms 62 ms 64 ms ten-0-1-0-1.cor01.syd04.nsw.VOCUS.net.au [175.45.72.76]
8 62 ms 63 ms 63 ms ten-0-1-0-0.cor01.bne03.qld.VOCUS.net.au [114.31.194.166]
9 63 ms 64 ms 65 ms ten-2-2-0.bdr01.bne03.qld.VOCUS.net.au [114.31.194.111]
10 63 ms 62 ms 64 ms as7496.qld.ix.asn.au [218.100.76.38]
11 64 ms 76 ms 65 ms gi2-38.core1.bne3.server-noc.com [203.147.255.233]
12 117 ms 67 ms 64 ms po93.mls1.bne3.server-noc.com [203.147.255.189]
13 343 ms 66 ms 64 ms www.nrl.com [202.148.153.145]

Trace complete.

Is this enough proof that the DNS server Vodafone are using are junk or am I using an old one?

r2b2

571 posts

Ultimate Geek

#1546114 3-May-2016 15:54

Those are the same ones I am using and I can do a nslookup just fine. You didn't include a nslookup in your original message but I assumed you tried that too and confirmed that the DNS server responding is one of those two that you have set?

Tradepub

Free professional, reference and technical white papers (affiliate link).

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1546117 3-May-2016 15:56

First step when you experience DNS issues is always to try a nslookup against the DNS servers to confirm they're working.

shrub

769 posts

Ultimate Geek

ID Verified

#1546141 3-May-2016 16:15

Yea the DNS server is responding just fine its the redirects that go nowhere. I also have another computer that is running google DNS and its not having any issues. This has been happening off and on for months I originally thought it was my router so I purchased a new....Is there any good reason to stay with the Vodafone defaults or just change the router to googledns?

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1546164 3-May-2016 17:00

shrub:

Yea the DNS server is responding just fine its the redirects that go nowhere. I also have another computer that is running google DNS and its not having any issues. This has been happening off and on for months I originally thought it was my router so I purchased a new....Is there any good reason to stay with the Vodafone defaults or just change the router to googledns?

Using 3rd party DNS should be avoided at all costs unless you're fully aware of the limitations (and why it's bad).

Brumfondl

1185 posts

Uber Geek

Trusted

#1546165 3-May-2016 17:05

Have you tried putting the DNS server entries into the IPv4 configuration on Windows instead of getting them from the router using DHCP? I found that this stopped the issues similar to yours that I was having.

shrub

769 posts

Ultimate Geek

ID Verified

#1547215 5-May-2016 14:52

I think I sorted it out. I changed to pi-hole using the Vodafone DNS and I've not had any issues yet. Its been running 2 days so far fingers crossed. If i do have issues ill just change the entire network to google/openDNS.