rDNS changed back to default

[#1]

Mine has reverted too. Support ticket hasn't even been acknowledged yet!
Anyway, normal service resumed...

[#2]

Same here, all fixed now.

[#3]

mine is fixed as well

[#4]

Just for awareness, problem 84655 was raised for this yesterday evening.
I would get more info but I've left my VPN fob in the office. I'm sure someone on CRT will give more of an update tomorrow on what happened.

[#5]

Noticed this had happened to mine as well. I was a little bit miffed as my plusnet username is my actual name!
However, they have only done half a job. Yes the PTR record has been put back for rDNS to <ip>.plus.com. However, there is no corresponding A record for forward lookups. They have left the A record of my Plusnet username tho. Sort it out Plusnet and stop fiddling!

[#6]

Why would you need a corresponding A record?

[#7]

Because it had one before all this under <IP>.plus.com. Also, the Internet filter at work blocks IP based URLs.

[#8]

So what's the issue with using a dynamic DNS service to point to you? That has the advantage of working whether you are on fixed or dynamic IP.

[#9]

or get a domain for a few quid a year.

[#10]

Quote from: Oldjim

I just did the same here http://mxtoolbox.com/ReverseLookup.aspx and mine has changed back as well Reported by ns2.force9.net on 2/7/2015 at 10:08:33 AM

ive just checked mine on that website and it has come back as mail.agcomputers.uk.com ????
where or what has that came from !!!

[#11]

Not sure, but that domain doesn't even exist any more. Quite possibly a custom rDNS entry belonging to a customer who was assigned the IP before you. Do you know what your rDNS was set to a few days ago, or is this the first time you've checked to see what it is?

[#12]

Interesting:

C:\Users\John>tracert mail.agcomputers.uk.com
Tracing route to mail.agcomputers.uk.com [205.164.14.88]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  tg582 [192.168.1.254]
  2    22 ms    22 ms    21 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186]
  3    21 ms    21 ms    21 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.176]
  4    31 ms    23 ms    20 ms  xe-1-2-0.pcl-cr01.plus.net [212.159.0.208]
  5    21 ms    20 ms    21 ms  ae2.pcl-cr02.plus.net [195.166.129.7]
  6    21 ms    21 ms    21 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
  7    20 ms    21 ms    23 ms  10gigabitethernet5-1.core1.lon1.he.net [5.57.80.128]
  8    24 ms    24 ms    23 ms  10ge5-2.core1.lon2.he.net [72.52.92.222]
  9    87 ms   107 ms    87 ms  100ge1-1.core1.nyc4.he.net [72.52.92.166]
 10   156 ms   170 ms   156 ms  10ge9-6.core1.sjc2.he.net [184.105.213.173]
 11   155 ms   162 ms   155 ms  10ge1-4.core1.sjc1.he.net [72.52.92.117]
 12   158 ms   157 ms   169 ms  energy-group-networks-llc.10gigabitethernet1-3.core1.sjc1.he.net [64.71.150.22]
 13   157 ms   157 ms   157 ms  205.164.14.88
Trace complete.

[#13]

I've a sneaking suspicion that will cease to happen once chenks76's rDNS has been corrected.

[#14]

Quote from: Bob

Not sure, but that domain doesn't even exist any more. Quite possibly a custom rDNS entry belonging to a customer who was assigned the IP before you. Do you know what your rDNS was set to a few days ago, or is this the first time you've checked to see what it is?

this is the first time i've checked it.

[#15]

Suspected as much.
I've corrected it, so things should look a little less unusual when the changes take effect. I'm not sure when that will be though, because I think the script that updates customers' rDNS is currently disabled whilst our engineers try to establish what happened over the weekend.