Virgin Media DNS IP Address change

[EffBee]

Hi all,

I have had Virgin Media DNS server IP addresses hard coded into my PCs' IP properties for years since I don't use their DHCP for various reasons.

This morning my home's computers were all failing to find web addresses, though things like Norton's LiveUpdate were fine.

It took me an expensive and frustrating 20 minute phone call to the script monkeys in VM's tech support area to persuade them to simply give me new DNS addresses so I could get Name Resolution working again. Ho-Hum. I only got these after becoming a bit firm and rejecting their contention that (1) they don't support fixed IP addresses, (2) my cable modem is fine (which I told them at the start) and (3) I must have a LAN hardware fault so I should get my local servicing agents to check my LAN hardware for faults since there was no problem at their end.

Everything fine now


Any idea why they changed DNS Addresses anyone? Phorms? Routine network reonfiguration?

They probably put up new servers ages ago and have only just turned off the old ones, which I was using.

 

[Duke]

Bit silly to set them manually then moan when they change them! You could have set it to auto and noted down the IPs?

 

[feriso]

Or you could just use OpenDNS?

 

[J.B]

I would have used OpenDNS or googles DNS to confirm that was the problem, then google around to find VMs DNS IP if your really wanted to go back to using their servers.

Using their DHCP would probably of been the easiest/quickest option. Why dont you use it anyway?

 

[EffBee]

I would have used OpenDNS or googles DNS to confirm that was the problem, then google around to find VMs DNS IP if your really wanted to go back to using their servers.

Using their DHCP would probably of been the easiest/quickest option. Why dont you use it anyway?

The VM cable modem feeds into a "Dirty" network card on a PC with Smoothwall runing off it. My LAN runs off a "Clean" network card on the smootwall box.

This was set up years ago, and a major rethink is long overdue - for one thing there is a new version of smoothwall out, and the PC I'm running smoothwall on is a Pentium 150 - old and noisy.

Working from memory of long ago the dirty side of the smoothwall box is using VM's DHCP.

I used to use the Smoothwall DHCP for my LAN but for the small number of devices I had, and the need for some of them to fixed like print servers and file servers, I changed them all to fixed IP.

As I said after many years of accepting the old philosophy of "If it ain't broke, don't fix it" I will have a close look at what I have, and a clsoe look at what could be improved. (Anti-Phorms and similar configuration for instance).

Fixed IP is OK till something changes, but this is only the second time since 2001 it has been an issue.

Thanks for all replies - even the semi critical ones

 

[EffBee]

Bit silly to set them manually then moan when they change them! You could have set it to auto and noted down the IPs?

Not sure if this would have worked with the Smootwall box in the way of the VM hardware. Probably should have tried though Trouble is I only mess with this stuff every couple of years and I forget the little tricks. I used to have an old PC to plug straight into the cable modem for just the ourpose you describe above - no worries about nastiness from the web that way.

 

[EffBee]

I would have used OpenDNS or googles DNS to confirm that was the problem, then google around to find VMs DNS IP if your really wanted to go back to using their servers.

Using their DHCP would probably of been the easiest/quickest option. Why dont you use it anyway?

I'm a bit out of touch on this stuff. I'll look into those things, and proxy server services while I'm at it.

 

[PistolPete]

When did they change them? I've had the same ones since I joined VM in 2008 and I've just checked and their system is still issuing the same IPs for the DNS resolvers.