Project

General

Profile

Bug #405

DNS error after popping hda out of and into network

Added by phillipe almost 11 years ago. Updated over 10 years ago.

Status:
Assigned
Priority:
Low
Assignee:
Category:
DNS
Target version:
-
Start date:
01/05/2010
Due date:
% Done:

0%


Description

I had to take my hda somewhere else, so I disconnected it from the network and let the router resume handling IP requests (turned DHCP on). Everything was just fine. When I hooked the hda back, though, it stopped resolving internet addresses. I can access the dashboard and the router from the hda itself, and the hda is also reachable by other machines in the network (dashboard-, remote desktop- and remote files-wise). The hda can ping 68.180.206.184, but yahoo.com is referred to as an unknown host, so I'm assuming that something goes wrong with the DNS whenever the hda is disconnected from the original network and/or the router's DHCP is turned on again.

I've tried turning the PC on with router's DHCP on, then tried turning it on with router's DHCP off and had no success either way. In both cases, the hda gets the static IP I've set as default during Amahi's installation and everything remains the same way I described above.

Also, when the router's DHCP is turned off, the HDA seems to serve an IP address to the other PCs on the network correctly. It seems to be working just OK, except it can't resolve internet addresses.

The HDA connects itself to the network by means of cable (and eth0 device) to a Linsys WAG200G router.

History

#1 Updated by cpg almost 11 years ago

  • Status changed from New to Assigned
  • Assignee set to cpg
  • Priority changed from Normal to Low

can you

ping 208.67.222.222
ping 208.67.220.220

these are the default DNS providers (OpenDNS).

Did the network change?
If so, use

hda-change-gw IP_OF_THE_ROUTER

also, can you tell us what step you get stuck at in the network troublshooter:

http://wiki.amahi.org/index.php/Network_Troubleshooting

#2 Updated by phillipe almost 11 years ago

cpg wrote:

can you

ping 208.67.222.222
ping 208.67.220.220

these are the default DNS providers (OpenDNS).

Did the network change?
If so, use

hda-change-gw IP_OF_THE_ROUTER

also, can you tell us what step you get stuck at in the network troublshooter:

http://wiki.amahi.org/index.php/Network_Troubleshooting

Yes, I can ping both.

1. ping hda (this ensures the dns server is working) - OK
2. ping router (this ensures your HDA can see the router) - OK
3. ping 68.180.206.184 (this ensures you can see the rest of the world) - OK
4. ping yahoo.com (this ensures your dns server can see the world) - FAIL (Unknown host)
5. in the HDA itself (if you can), access http://hda - OK

By the way, the hda-change-gw script, as well as the hda-change-dns, aren't working due to misused quotes (should be double, used single). You pointed it out to me yourself, but it seems like they haven't been updated yet. Just a reminder. :)

My network didn't change, but I tried using the script anyway and got:

DBD::mysql::st execute failed: Table '$m_database.settings' doesn't exist at /usr/bin/hda-change-gw line 81.
Couldn't execute statement: Table '$m_database.settings' doesn't exist at /usr/bin/hda-change-gw line 81.

#3 Updated by cpg almost 11 years ago

ok, so DNS is not working.

btw, the fixes are coming in Amahi 5.1 here is the latest release with them:

http://alpha.amahi.org/tmp/hdactl-3.0-5.i386.rpm

(that is the 32b - change appropriately for 64b)

do this before and after installing the above rpm (with rpm -Uvh ...):

service named status

and paste the putput here ...

#4 Updated by phillipe almost 11 years ago

cpg wrote:

ok, so DNS is not working.

btw, the fixes are coming in Amahi 5.1 here is the latest release with them:

http://alpha.amahi.org/tmp/hdactl-3.0-5.i386.rpm

(that is the 32b - change appropriately for 64b)

do this before and after installing the above rpm (with rpm -Uvh ...):

service named status

and paste the putput here ...

Did it. Brought up the terminal, switched to root user and used the rpm -Uvh <package's path> command in between two service named status executions. The outputs were as follows:

[root@desktop-server Download]# service named status
version: 9.6.1-P2-RedHat-9.6.1-13.P2.fc12
CPUs found: 1
worker threads: 1
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 1704) está em execução*...
[root@desktop-server Download]# rpm -Uvh hdactl-3.0-5.i386.rpm
Preparando... ########################################### [100%]
1:hdactl ########################################### [100%]
[root@desktop-server Download]# service named status
version: 9.6.1-P2-RedHat-9.6.1-13.P2.fc12
CPUs found: 1
worker threads: 1
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 28497) está em execução*...

*means "is running" in portuguese

As of right now, the HDA is still unable to resolve internet addresses. I haven't rebooted it yet and the router's DHCP is off.

#5 Updated by cpg almost 11 years ago

weird.

cat /etc/resolv.conf

#6 Updated by phillipe almost 11 years ago

cpg wrote:

weird.

cat /etc/resolv.conf

search home.com
nameserver 192.168.91.3 (HDA's IP)

#7 Updated by cpg almost 11 years ago

ok, looks good.

next you can try:

hda-change-dns IP1 IP2

where IP1 and IP2 are your providers dns , in case they are blocking OpenDNS.

you can try google's dns with:

hda-change-dns 8.8.8.8 8.8.4.4

to get back to opendns:

hda-change-dns 208.67.222.222 208.67.220.220

#8 Updated by phillipe almost 11 years ago

Still, no success. But I think it could be my fault. hda-change-dns was not working, so I tweaked it myself (changed single quotes to double quotes in two of its lines).

#9 Updated by cpg almost 11 years ago

wait!

when did you have to change hda-change-dns?!?!

it should be fixed by now in the hdactl you installed!!

#10 Updated by phillipe almost 11 years ago

Oh, I actually tweaked it before updating. So now it should be the official one once again.

#11 Updated by Anonymous over 10 years ago

  • Category set to DNS

Also available in: Atom