"Unknown" gateway

[#1]

Getting the following message from the gateway checker, it has happened a number of times over the last few weeks.
It is not causing me any problems.
Sorry, the tool currently could not identify your gateway; this does not mean that anything is wrong with your connection.
Reverse traceroute from giganews
news-europe.giganews.com
1 vl201.gw2.ams.giganews.com (216.196.110.2) 1 ms 0 ms 0 ms
2 vl305.gw1.ams.giganews.com (216.196.108.226) 0 ms vl306.gw1.ams.giganews.com (216.196.108.234) 0 ms 216-196-108-178.ams.giganews.com (216.196.108.178) 0 ms
3 linx-gw1.plus.net (195.66.224.164) 7 ms 7 ms 7 ms
4 te2-3-711.ptw-gw01.plus.net (84.92.4.229) 7 ms 7 ms 7 ms
5 vl603.ptw-gw01.plus.net (84.92.4.161) 8 ms 8 ms 10 ms
6 * * *
7 * * *
8 * * *
Max number of unresponsive hops reached (firewall or filter?)

[#2]

Thanks for that traceback. Looks like 84.92.4.161 might not be what the reverse DNS says.
What do you get from tracert ntp.plus.net ?
David

[#3]

As requested
N.B. Router's IP address removed
Pete
tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.6.10]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  XXX.XXX.XXX.XXX
  2    30 ms    30 ms    30 ms  lo0.plusnet.ptw-ag02.plus.net [195.166.128.93]
  3    29 ms    30 ms    29 ms  gi1-10-603.ptw-gw01.plus.net [84.92.4.160]
  4    29 ms    31 ms    30 ms  po6.ptn-gw02.plus.net [212.159.1.137]
  5    29 ms    29 ms    29 ms  vl55.ptn-lb01.plus.net [212.159.2.124]
  6    29 ms    29 ms    29 ms  cdns02.plus.net [212.159.6.10]
Trace complete.

[#4]

Thanks. Your gateway currently is ptw-ag02 in Telehouse West. So it looks like 84.92.4.161 probably needs a different reverse DNS entry. I'll raise this with Plusnet.
David

[#5]

Thanks for flagging this up guys, we'll make sure this gets addressed ASAP.

[#6]

Our engineers are aware and will correct the rDNS entries at the next available opportunity (ref: 69999).

[#7]

Another one for Bob / David
PeteB
Reverse Traceroute
1 vl201.gw2.ams.giganews.com (216.196.110.2) 0 ms 0 ms 0 ms
2 216-196-108-178.ams.giganews.com (216.196.108.178) 0 ms 216-196-108-186.ams.giganews.com (216.196.108.186) 0 ms vl307.gw1.ams.giganews.com (216.196.108.242) 0 ms
3 linx-gw1.plus.net (195.66.224.164) 7 ms 7 ms 9 ms
4 vl704.ptw-gw01.plus.net (84.92.4.249) 36 ms 16 ms 9 ms
5 * * *
6 * * *
7 * * *
Max number of unresponsive hops reached (firewall or filter?)

tracert
C:\Users\admin>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.6.10]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  XXX.XXX.XXX.XXX
  2    34 ms    29 ms    27 ms  lo0.plusnet.ptw-ag01.plus.net [195.166.128.101]
  3    26 ms    27 ms    27 ms  gi1-5-704.ptw-gw02.plus.net [84.92.4.248]
  4    27 ms    27 ms    27 ms  ae4.ptw-cr02.plus.net [195.166.129.38]
  5    28 ms    28 ms    27 ms  te9-4.ptn-gw02.plus.net [195.166.129.35]
  6    27 ms    27 ms    26 ms  vl55.ptn-lb01.plus.net [212.159.2.124]
  7    27 ms    27 ms    28 ms  cdns02.plus.net [212.159.6.10]
Trace complete.

[#8]

Thanks, 84.92.4.249 needs its rDNS amending to ptw-ag01 style.
David

[#9]

Thanks for the heads up. I'll have a word with our engineering folk and ask for the rDNS to be updated ...

[#10]

Hi Peteb,
Can you supply your account username please?
The issue in your last trace does not relate to a missing/incorrect rDNS record.
84.92.4.249 is one of our core routers and is not one of our DSL gateways, so the rDNS is accurate. The trace from Giganews shows another issue though, but I need your account details so I can run some captures from Usertools.

[#11]

As requested, PM sent with account username.
PeteB