Suddenly when doing an IPCONFIG /ALL (as you do, occasionally) I find that instead of the usual null following the "DNS suffix search list" and "Connection-specific DSN suffix" lines I now have "cable.virginmedia.net". This has the unusual effect of giving me a completely non-192.168.m.n IP address for one PC when PINGed from the other PC, in fact an 'external' one 82.33.x.y.
Can anyone think that there could be more serious problems in what Virgin Media calls an 'advanced network error search enhancement', or some such?
I've asked for it to be turned off for me, but it would seem I have to clear a cache somewhere, probably browser...
Thanks!
Connection-specific DNS suffix - possible problems?
-
- PlatinumLounger
- Posts: 5408
- Joined: 24 Jan 2010, 08:33
- Location: A cathedral city in England
Connection-specific DNS suffix - possible problems?
John Gray
"(or one of the team)" - how your appointment letter indicates you won't be seeing the Consultant...
"(or one of the team)" - how your appointment letter indicates you won't be seeing the Consultant...
-
- Administrator
- Posts: 12604
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connection-specific DNS suffix - possible problems?
John,
You can get those DNS suffixes from two places:
The way these are used is that if you lookup a hostname that is not fully qualified, for example
\\server\fileshare
then your computer will try each of those suffixes to try and find a match, so in your case it will try
\\server.cable.virginmedia.net\fileshare
If you don't like the searches that your ISP is doing then you could configure your computers (or your router) to use a completely different DNS server if you want. For example I have my router configured to use OpenDNS instead of my ISP's DNS servers.
You can get those DNS suffixes from two places:
- The DHCP server on your network, this will probably be your ISP provided router
- The TCP/IP setup on your local computer
The way these are used is that if you lookup a hostname that is not fully qualified, for example
\\server\fileshare
then your computer will try each of those suffixes to try and find a match, so in your case it will try
\\server.cable.virginmedia.net\fileshare
If you don't like the searches that your ISP is doing then you could configure your computers (or your router) to use a completely different DNS server if you want. For example I have my router configured to use OpenDNS instead of my ISP's DNS servers.
StuartR
-
- PlatinumLounger
- Posts: 5408
- Joined: 24 Jan 2010, 08:33
- Location: A cathedral city in England
Re: Connection-specific DNS suffix - possible problems?
Thanks, Stuart - I found that "cable.virginmedia.net" had appeared in one of my router settings, so (shortened account!) I turned it off at the VM end and in the router, then rebooted the PC and the router and the cable modem, and the IP addresses have gone back to their normal 192.168.m.n format.
The matter was complicated because my homeplug WAP seemed not to be passing through DHCP from the router to laptops, and there the only thing that worked was a reboot of the homeplug WAP - swapping among assorted wireless USB devices did nothing...
The matter was complicated because my homeplug WAP seemed not to be passing through DHCP from the router to laptops, and there the only thing that worked was a reboot of the homeplug WAP - swapping among assorted wireless USB devices did nothing...
John Gray
"(or one of the team)" - how your appointment letter indicates you won't be seeing the Consultant...
"(or one of the team)" - how your appointment letter indicates you won't be seeing the Consultant...
-
- Administrator
- Posts: 12604
- Joined: 16 Jan 2010, 15:49
- Location: London, Europe
Re: Connection-specific DNS suffix - possible problems?
In my experience these things always turn into a long saga.John Gray wrote:...(shortened account!)...
Glad you got it fixed.
StuartR