wierd DNS problems

[122.45]

Hi all

At home I'm running Pipex ADSL via a Netgear router, and find that there are a very few websites that I cannot access - the browser just times out with a "network problem" kind of error. These aren't dodgy websites :rolleyes: (Sun's Java SDK download page and MBNA's online banking are the two that i've found). The wierd thing is that if I ping them, the DNS lookup is totally wrong, e.g.

> ping www.mbnanetaccess.co.uk

Pinging www.mbnanetaccess.co.uk [192.189.32.91] with 32 bytes of data

Now I guess there's my problem - I rather doubt that MBNA are really sitting on 192.189.32.91 - but virtually everything else is ok. nslookup gives two IP addresses, both on the 192.x.y.z network. There's nothing in the HOSTS file that could cause this, ipconfig /flushdns doesn't do anything either. I don't think it's the router, because I've just switched from a different one and I had the problem with that as well.

If I log on to my work computer via a VPN then things are fine, different DNS I guess? So, what's up - and how do I fix it?

[Memetic]

Have you tried setting a different DNS in the router?

Have you tried talking to Pipex support, they are generally pretty helpful.

[E-Liam]

Hi 122.45,

http://www.samspade.org/t/lookat?a=192.189.32.91

If that helps..

Cheers

Liam

[pilot-lite]

That IP appears appears to be the correct one for your bank.

There are "protected" IP ranges for use within networks, listed below.


Class A: 10.0.0.0 to 10.255.255.255

Class B: 172.16.0.0 to 172.31.255.255

Class C: 192.168.0.0 to 192.168.255.255

Class D: 224.0.0.0 to 239.255.255.255


Note that the bank's IP fall outside these ranges.

I'd be looking at the router configuration to see if thinks all 192.x.y.z address are internal to the network.

Hope this puts you on the right track...:ok:


pilot-lite

[122.45]

Ah! Being a total thicko I thought that all of 192 was reserved :O

After that, it was easy. The router is using DHCP to give out IP addresses - with a netmask of 255.0.0.0 (defined by me on this router, and on the old one, because I thought that it's what i needed). Switch to 255.255.255.0 and suddenly MBNA appears.

:ugh:

Thanks everybody. And there was I thinking that I understood a bit about networks.

Will.

[Evo]

Don't worry, you're not the first... :O

[OzPax1]

How about killing a DNS for a whole network....Like I did recently! :uhoh:


Teach me to muck about with dns view!