Amahi Forums

Hi all,

I aplogize if this has been covered before, but I am not seeing anything when I search for it.

So I have a generic p4 system running my Amahi install. The install went fine, and I was able to install the packages with out a problem. So after the install I turned off DHCP on my router in hopes to use Amahi for this purpose.

After a reboot however I am not able to access the internet at all (from the hda or my own systems). I figured it was a router issue, but it turns out my actual internet traffic is working fine but DNS is not.

From my amahi box I can ping my other systems (192.168.0.{100-150}), and ping my router (192.168.0.10).

I am able to confirm the system has a valid dns server in the database (select * from settings where name like '%dns%';).

One weird thing that jumped out to me is that my resolve.conf file is showing a the hda's ip address as the name server (is this correct?).

When I change the IP on this to something like 4.2.2.2 I am able to access the internet. I am currently using synergy+ on the HDA so i have a keyboard but will nuke that later on.

I am also able to telnet to port 53 from other systems on my network to the hda.

I'm kind of at a loss here as to what the problem can be. Let me know if anyone has any ideas.

Thx,
Ryan

One weird thing that jumped out to me is that my resolve.conf file is showing a the hda's ip address as the name server (is this correct?).

yes, your hda is a caching DNS server. will provide the local names as well as faster resolution for repeat hits.

can you ping 208.67.222.222 and 208.67.220.220 (the default opendns servers)?

if not, maybe your provider blocks these guys?

if u can ping them, can you check if it returns 72.249.190.156 with
also see the how to change DNS provider page. you can change them to the Google Public DNS, to your ISP, etc.

looks like 4.2.2.2 is a DNS provider ... you can use that too.

Thanks cpg for the reply, I am able to ping those IP's.

if u can ping them, can you check if it returns 72.249.190.156 with

Code: Select all

Code: nslookup amahi.org 208.67.222.222

So when I do the command has you have it here I get the following It looks like it is working when I specify the server, but when I don't specify a dns server (I assume it uses the local one) i get the following

I am thinking something is getting gummed up on the dns request itself, like the server is not passing it along or something like that.

Could it possibly be that the DNS service is not totally running on the local system?

When I run 'ps aux | grep dns', I get nothing returned. Should I see some sort of service in top, or even in the ps list?

**EDIT** I think am assuming the service is called 'named' that is being used for DNS resolution, and it is running.

Also, when I check /var/log/messages, I am seeing the following ... so chasing that now.

We had someone yesterday with a "transparent" proxy cache (clarkconnect) that was incorrectly caching the repo files and basically rendering them useless (looked like repo corruption and generally a pissed-off user against Amahi - though we traced it to clackconnect).

do you have a router or something that could be messing with the traffic?

if you can do the lookup from the server but not using your local "named" server (yes, that is the name of the DNS server), then there may be someone gummed up in named.

i assume you already tried hdactl-hup and rebooting?

I don't think so, unless there is some magic foo enabled on my router that I don't know about. OH yeah I have rebooted this stupid system more times than is prolly healthy

I have done so much to the system at this point I am going to nuke it and start over. If I end up here after that no big deal, just wont use it as the dns server, its all good

To be honest I bounced it off of some of my buddies at work (linux admins who work with bind on a regular basis) and they had no clue what was going on.

I'll let y'all know how it goes, thanks for all the assistance, this really seems like an awesome system.

thx,

Wachu

Not to insult wachuwamekil, I had the the same problem, turn out to be that I turned off the wrong "DHCP".

See example below. I disabled Wan connection type (the upper one) instead of the Network address settings.
This is using DD-WRT v24sp1.

Salo

Good luck it's worth it!!