General Broadband domain name change - Page 4

qasdfdsaq · 23-10-2013, 12:24

Quote:

Originally Posted by General Maximus

Or does it just look at the host info cpc24-linc11-2-0-custxxx.xx-x.cable.virginmedia.com and say "oh yeah, it ends in .virginmedia.com therefore it is a VM address?

That's pretty obviously what it does, considering that's basically the entire point of the tool

Kushan · 23-10-2013, 19:37

Quote:

Originally Posted by kwikbreaks

No need imo but commenting that there had been a weeks notice when it only appeared as a post on the forum is a pretty dumb comment (again imo).

Yeah, to be honest I agree with you as well here. A single forum post doesn't really count as much notice in my opinion, but I don't think Virgin was obligated to give any notice at all.

All that stuff about logging RDNS and such, I'm not really sure I want Virgin logging anything unless they explicitly have to but that's just me.

qasdfdsaq · 23-10-2013, 21:36

Well as it is they already log tons of stuff they don't have to, your usage and traffic for STM purposes for one, sending you letters complaining they don't like the way you're using your "unlimited" connection being another, but that's another thread entirely.

BenMcr · 23-10-2013, 21:56

Quote:

Originally Posted by General Maximus

As business broadband is seperate from residential I defo think an email or letter should have gone out to all business accounts and then they could have decided whether it would affect them or not. Making a post on a forum for residential customers which VM admit to it not affecting so much is a poor attempt at comunication. It is like Tesco's telling you that you can't pay for your shopping by card anymore and making the announcement on a chat forum on their website; it isn't the most informative method.

I have no idea what notification process VM Business are doing for their connections, but as far as I'm aware, the post Mark put up was aimed at residential customers.

**Paul** · 27-10-2013, 14:52

Updated the detector for virginm.net

Kushan · 27-10-2013, 15:06

Quote:

Originally Posted by Paul M

Updated the detector for virginm.net

Yup, works:

qasdfdsaq · 27-10-2013, 15:56

Sweet, and it still works on the old ones:

Connection Information You appear to be on a Virgin Media Connection IP address 94.175.249.245 Host host-94-175-249-245.not-set-yet.virginmedia.net

**Paul** · 27-10-2013, 16:17

Quote:

Originally Posted by qasdfdsaq

Sweet, and it still works on the old ones:

I actually removed some really old definitions from the list (ntl & blueyonder).

qasdfdsaq · 27-10-2013, 16:24

Ah. Yeah those aren't just old they're ancient :-P been a while since I've seen any of those

Kushan · 27-10-2013, 18:15

Only about 4 or 5 years since I seen one of those, which isn't that long in VM fix times =P

qasdfdsaq · 27-10-2013, 18:52

Hehehe

Chrysalis · 29-10-2013, 15:11

Quote:

Originally Posted by General Maximus

lol, nice attempt to blur out 82.5.27.121 (not sure about the 5)

why has he blurred it out anyway?

just do this

C:\windows\system32>nslookup cpc17-warr6-2-0-cust120.1-1.cable.virginm.net.
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: cpc17-warr6-2-0-cust120.1-1.cable.virginm.net
Address: 82.8.27.121

General Maximus · 29-10-2013, 17:45

brilliant

Kushan · 30-10-2013, 09:53

Can we all stop hacking Kushan, please?

Qtx · 30-10-2013, 11:15

Requesting my post be deleted!