Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Community Manager
1,040 Views

DNS resolution won't work

Hi folks,

DNS name resolution doesn't work on the Edison. I would say there are two problems:

1) Irrespective of what's written in /etc/resolv.conf, name resolution does not work.

2) The nameserver in /etc/resolv.conf always gets overwritten with 192.168.0.1, which won't work for me. I replaced it with google's name server, but the change gets reverted after reboot.

Any hints are appreciated.

3 Replies
Highlighted
Community Manager
4 Views

Ok, I actually got it wrong. It's not only a name resolution problem as I first assumed. No address outside of the internal network (192.168.0.x) is reachable, not even by IP.

However, I can ssh to the Edison from another Computer in the same network and ping back and forth.

ifconfig says:

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1008 (1008.0 B) TX bytes:1008 (1008.0 B)

wlan0Link encap:Ethernet HWaddr 78:4b:87:a6:97:1e inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4412 errors:0 dropped:0 overruns:0 frame:0 TX packets:5188 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:326171 (318.5 KiB) TX bytes:693169 (676.9 KiB)
Highlighted
Community Manager
4 Views

Hi checkfrog,

 

 

Have you tried flashing your Edison module? /docs/DOC-98643 https://communities.intel.com/docs/DOC-98643. You should be able to edit the /etc/resolv.conf file, so the Edison overwriting the address is not normal, connecting to other addresses outside the internal network should also be possible, so I'm guessing this might be a corrupted image.

 

 

Regards,

 

Pablo
0 Kudos
Highlighted
Community Manager
4 Views

Hi Pablo,

thanks for your reply. It is resolved now, but the main culprit was probably not the corrupted image. Actually, changing the assigned IP within the same subrange suddenly resolved the issue. I am not sure whether it was a router misconfiguration or some problem with the Edison, but for some reason it works now...

Thanks