dns1.rnc.net.cable.rogers.com [64.71.255.198]

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I've Been Here Awhile
Posts: 3

dns1.rnc.net.cable.rogers.com [64.71.255.198]

 

What does this mean? when I automatically connect online I am given two DNS numbers 64.71.255.198 & 64.71.255.204
I have pinged and traced all my connection info and these are the only two with time outs I am really fed up with lagging off the internet and failing to connect to the internet

C:\Users\Jamesporter>tracert 64.71.255.198
Tracing route to dns1.rnc.net.cable.rogers.com [64.71.255.198]
over a maximum of 30 hops:
1 13 ms 10 ms 9 ms 7.30.0.1
2 14 ms 11 ms 11 ms 24.156.137.137
3 12 ms 11 ms 11 ms 69.63.250.29
4 17 ms 11 ms 11 ms so-4-0-0.gw02.wlfdle.phub.net.cable.rogers.com [
66.185.82.97]
5 10 ms 10 ms 12 ms gw01.wlfdle.phub.net.cable.rogers.com [66.185.93
.65]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


C:\Users\Jamesporter>ping 64.71.255.198
Pinging 64.71.255.198 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 64.71.255.198:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


C:\Users\JamesPorter>tracert 64.71.255.204

Tracing route to 64.71.255.204 over a maximum of 30 hops

1 8 ms 7 ms 8 ms 7.30.0.1
2 11 ms 7 ms 7 ms 24.156.158.169
3 11 ms 11 ms 11 ms 69.63.248.173
4 12 ms 11 ms 15 ms 69.63.250.21
5 12 ms 13 ms 10 ms gw01.wlfdle.phub.net.cable.rogers.com [66.185.93
.65]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


C:\Users\JamesPorter>ping 64.71.255.204
Pinging 64.71.255.204 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 64.71.255.204:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

***edited labels***

Solved! Go to Solution.
Resident Expert
Resident Expert
Posts: 13,884

Re: dns1.rnc.net.cable.rogers.com [64.71.255.198]

The two Rogers DNs servers, may not be traceable / routable.

Generally a DNs shouldn't change your speed other than the initial time for it to resolve an address.

All that being said, the Rogers ones seem to have had alot of issues and outages since the beginning of this year.

You can change your DNs server if you wanted to, say to something like google or similar (I am using them on my pc's etc at home, but phones ect are using the Rogers ones)

If you would like help changing your DNs, myself or some of the others will likely be able to help.


I've Been Here Awhile
Posts: 3

Re: dns1.rnc.net.cable.rogers.com [64.71.255.198]

How is it legal for Rogers to keep raising prices and adding more fees when they are not providing the internet service and I have to find and pay for 3rd party servers in order to connect online because the Rogers servers are always down

I remember Rogers advertising Canada's most reliable network what was that about?

I made the post in Hopes Rogers would see that there servers are down and fix them but I am guessing it was brushed off

Resident Expert
Resident Expert
Posts: 13,884

Re: dns1.rnc.net.cable.rogers.com [64.71.255.198]

This is a user to user forum primarily, not the best place to pass on that info to Rogers. Smiley Sad

You do not have to pay for anything extra server wise. The google ones are very reliable and preferred, and completely free.

Unfortunately Rogers (and just about every provider) have a wonderful legal document called a terms of service or terms of use. And in these they usually say that they can not guarantee the service to always work Smiley Sad

The servers while are ocassionaly slow to respond and have been fully down for a day or two, if you are continually having issues there may be some other issue going on. I use both google and Rogers DNs servers here, and generally both are about the same on a day to day basis (other than the few trouble days)

But I 100% agree they need to fix the stability on them.


I've Been Here Awhile
Posts: 3

Re: dns1.rnc.net.cable.rogers.com [64.71.255.198]

Rogers just blows me off on the phone and live txt support and denies it I thought maybe some of the Rogers networking admins might monitor the forum and fix there servers but I see rogers doesn't have support for the service they provide another 1 that doesn't work so-4-0-0.gw02.bloor.phub.net.cable.rogers.com [64.71.240.166] beginning to consider Teksavvy or Verizon when they come to Canada as an alternative to Rogers, Rogers servers are down for months and years at a time not days or hours
Resident Expert
Resident Expert
Posts: 13,884

Re: dns1.rnc.net.cable.rogers.com [64.71.255.198]

I generaly have no issues with the rogers DNS servers on the devices i have them on (all my wireless devices except 1 laptop).. they all resolve on a daily basiss.
BUT.. different areas, may reslove through different DNS servers. 
(IE: the two i am given, is 64.71.255.204 and 64.71.255.198 and i have only had 2 outages so far this year).

 

 

Now.. the issue you are having, MAY not be DNS related.
so-4-0-0.gw02.bloor.phub.net.cable.rogers.com
Is a seperate node, i BELEIVE at one of the POI's.   Recently, these have been all been switched over to newer ones, to allow companies like Techsavvy, etc to gain FULL access to all of the rogers serviced areas (compared to before only had select ones)  This one i beleive from what i could find, was only switched in the last month or so.. and many have been complaining of issues with it.

Now, again, this is a SHARED node... this is one that both ROGERS and techsavvy traffic go through, so if it is specificaly a node issue.. switching companies, would not make a difference in this case (unless you went with a DSL or fibre provider, which would route differently.

 

(just checked a bunch of tracerts from where i am.. again, different location, i go through a different node, so i am not effected)

 

Worth a shot.. though i dont think it would change anything, could try an alternate DNS server.. see if it takes you another route.  I beleive places like techsavvy dont use their own dns servers, and solely use a public one.. so worth maybe a temp change to one of them.

 

This IS 100% a rogers thing to fix, its their node.  Just making you aware, if you do descide to change, that it may not fix the issue.