Amahi Forums

Hi ,

When ever I try to access the web interface of my server using the amahi.net address in my browser it always sends me to the internet troubleshooting page. However if I try to access it using either hda/ or amahi.org/ both resolve to my server's dash board/control panel. The trouble is that some apps use the amahi.net address and so fail to work. Any ideas?

To confirm hda/ resolves to the anmahi Dashboard while amahi.org/ resolves to the control Panel. Amahi.net always goes to the internet home trouble shooting page?

Recommend you check out the network troubleshooting wiki page.

BTW, what is the domain you chose for your server on amahi.org?

the domain was amahi.org

When you created your HDA profile on amahi.org, it defaults to amahi.net. Did you change that to something else?

the domain was amahi.org

Best not to use a domain you do not own. Either leave it at the default value or change it to something not already used on the internet unless you own a domain.

Also is your HDA the DHCP and DNS server for your network? If http://hda/ brings up the dashboard, then it is properly set up.

Please provide the URL for the following from the command line on your HDA:

Hi mate,

The problem is not actually on the server but everything else connected to the server. If I do NSlookup on the server via SSH both IP and domain will resolve correctly as follows:

[root@amahinet Tighernain]# nslookup 8.8.8.8
Server: 192.168.1.10
Address: 192.168.1.10#53

Non-authoritative answer:
8.8.8.8.in-addr.arpa name = google-public-dns-a.google.com.

Authoritative answers can be found from:

[root@amahinet Tighernain]# nslookup google-public-dns-a.google.com
Server: 192.168.1.10
Address: 192.168.1.10#53

Non-authoritative answer:
Name: google-public-dns-a.google.com
Address: 8.8.8.8

But if I do exactly the same on any of the computers attached to the server I get the following:

PS C:\WINDOWS\system32> nslookup 8.8.8.8
Server: amahi.amahi.net
Address: 192.168.1.10

Name: google-public-dns-a.google.com
Address: 8.8.8.8

PS C:\WINDOWS\system32> nslookup google-public-dns-a.google.com
Server: amahi.amahi.net
Address: 192.168.1.10

Non-authoritative answer:
Name: black.amahi.org
Address: 208.115.201.203
Aliases: google-public-dns-a.google.com.amahi.net

As you can see the domain resolves back to amahii.org IP address. However if I add a single full stop to the end of the Google DNS servers name NSlookup will resolve the Domain correctly as follows:

PS C:\WINDOWS\system32> nslookup google-public-dns-a.google.com.
Server: amahi.amahi.net
Address: 192.168.1.10

Non-authoritative answer:
Name: google-public-dns-a.google.com
Addresses: 2001:4860:4860::8888
8.8.8.8

This is true for every domain I have tried. I have tried changing from OpenDNS to google's open DNS servers but no change. My router is a Linksys XAC1200 with DHCP and DNS off, NAT on, I have one D-Link 1200 wireless repeater in bridge mode and a couple of dump switches forming the network. Then about 36 clients varying from 5 PC's and Laptops, 4 consoles, a printer, and the usually smart devices.

Many Thanks in advance for your help.

URL follows:

https://paste.fedoraproject.org/521216/48380002/

Hi mate,

One last thing If I do a NSlookup directly on an authoritative name server everything works.

PS C:\WINDOWS\system32> nslookup www.google.com ns1.google.com
Server: ns1.google.com
Address: 216.239.32.10

Name: www.google.com
Addresses: 2404:6800:4006:806::2004
122.150.1.24
122.150.1.39
122.150.1.29
122.150.1.45
122.150.1.55
122.150.1.59
122.150.1.44
122.150.1.20
122.150.1.50
122.150.1.34
122.150.1.40
122.150.1.30
122.150.1.25
122.150.1.49
122.150.1.54
122.150.1.35

as apposed to:

PS C:\WINDOWS\system32> nslookup www.google.com
Server: amahi.amahi.net
Address: 192.168.1.10

Non-authoritative answer:
Name: black.amahi.org
Address: 208.115.201.203
Aliases: www.google.com.amahi.net

There are a couple of issues here:

One of them is that of using amahi.org within your network. One of the side effects of that is that the amahi.org services on the internet may not be visible, including repos, API, mirrors, dynamic DNS, etc. That means you may not be able to see apps, install apps, update dynamic DNS, and more. Or if you can use some of these, others may not work or may work partially in arbitrary and strange failure modes.

The second one is about the google.com DNS resolution issues, clients are typically known in the last few years for caching DNS queries, sometimes aggressively, and incorrectly others. I would suggest power cycling the clients and trying again.

Sorry I double checked and I am only using amahi.net within my network and not Amahi.org my mistake.

The problem is with any domain lookup from a client not just google.

I have tried power cycling all clients and no change.