[SOLVED]Network Issue - DNS Resolution Anomaly

[Wirezfree]

Hi,

Bit of a strange one, or I'm being stupid..!!, LL2 on my HP Laptop

Have installed a new Wireless Router(Asus N66) connected to my Broadband Modem.
The install set-up all seemed fine, Router connected to my ISP and I can see WAN & DNS addresses O.K
However, when I open my Browser, "Page Cannot Be Displayed" , So open a terminal and do some pings:

BBC By IP:

Code:

dave@hp-laptop:~$ ping 212.58.244.119
PING 212.58.244.119 (212.58.244.119) 56(84) bytes of data.
64 bytes from 212.58.244.119: icmp_seq=1 ttl=53 time=21.9 ms
64 bytes from 212.58.244.119: icmp_seq=2 ttl=53 time=21.2 ms
64 bytes from 212.58.244.119: icmp_seq=3 ttl=53 time=21.5 ms
^C
--- 212.58.244.119 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 21.264/21.586/21.944/0.278 ms

BBC News By url:

Code:

dave@hp-laptop:~$ ping news.bbc.co.uk
ping: unknown host news.bbc.co.uk
dave@hp-laptop:~$

So...
I think DNS, recheck router all seems fine, to further test fire up my daughters Windows laptop connect to router that works fine....

Then... I add a DNS Server manually to the connection in LL2 in the connection manager settings, re-start it, and ping again

BBC News By url:

Code:

dave@hp-laptop:~$ ping news.bbc.co.uk
PING newswww.bbc.net.uk (212.58.244.61) 56(84) bytes of data.
64 bytes from bbc-vip106.telhc.bbc.co.uk (212.58.244.61): icmp_seq=1 ttl=53 time=21.4 ms
64 bytes from bbc-vip106.telhc.bbc.co.uk (212.58.244.61): icmp_seq=2 ttl=53 time=21.0 ms
64 bytes from bbc-vip106.telhc.bbc.co.uk (212.58.244.61): icmp_seq=3 ttl=53 time=21.5 ms
64 bytes from bbc-vip106.telhc.bbc.co.uk (212.58.244.61): icmp_seq=4 ttl=53 time=21.5 ms
64 bytes from bbc-vip106.telhc.bbc.co.uk (212.58.244.61): icmp_seq=5 ttl=53 time=21.7 ms
^C
--- newswww.bbc.net.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 21.058/21.468/21.731/0.275 ms
dave@hp-laptop:~$

So that works, and also web browsing now works.... So I'm now a bit confused.??

The only thing I can think of.?
My new router's LAN is in a different IP range compared to previous...
So as LL/Network Manager got the old router settings cached.?, and adding the DNS manually is overriding that.?

Any suggestions/ideas welcome.
Thanks... Dave

[N4RPS]

Hello!

If your new router's LAN is now in a different subset, it would definitely change your previous connection settings.

Your specifying DNS manually seems to have fixed your issue, as would deleting the old connection and creating a new one. However, you know what they say - "If it's fixed, don't break it again"...

73 DE N4RPS
Rob

[Wirezfree]

Hi,

Yes.. It is working, be nice if it worked correctly though.??
I have found there is a lot of stuff on how DNS works in Linux
Also lots of differing opinions on how to fix DNS server anomaly's.

I was hoping it would be as simple as

Code:

ipconfig /flushdns

But thats another OS...

Thanks... Dave

[Wirezfree]

Just add extra DNS on connection in Connection Manager