Amahi Forums

Hello everybody

Situation:
I set up Amahi the following way
- Hostsystem: Xubuntu 14.04 LTS
- Amahi 7 (64bit) runs on Virtualbox 4.3.10 (from official repos)
- In Virtualbox I use Bridged Adapter settings and I am able to ping anything including http://f19.amahi.org (IP: 208.115.201.197).
- DHCP/DNS are turned off since I am in system where I don't have the permission to turn off the routers DHCP/DNS
- Amahi HDA can be reached from any computer in the network using its IP.

--> I would like to add greyhole to Amahi which results in following problem

Problem:
I cannot connect to the repos of http://f19.amahi.org resulting in the message of something like "no more mirrors". On the Internet I figured or with a following would solve the problem. But I got the output I found in an other thread in the forum too (viewtopic.php?f=9&t=5857&hilit=trying+o ... r&start=10) stating:

ok i think i might have the network issue resolved but i am getting this now

Code: Select all

root@nasserver ~]# yum install nano Loaded plugins: fastestmirror http://f19.amahi.org/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: f19.amahi.org; Unknown error" Trying other mirror. Error: failure: repodata/repomd.xml from amahi: [Errno 256] No more mirrors to try. http://f19.amahi.org/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: f19.amahi.org; Unknown error" [root@nasserver ~]#

Rebooting does not help.

Additional Info:
When I tried to activate/configure the app DLNA on my HDA i was redirected to the interactive troubleshooting page. So I went through http://dlna.amahi.net/amahi7interactive.html stoping at

Troubleshooting for Step 4 - DNS Resolving for Internal Hostnames

going through the commands an yielding http://pastebin.ubuntu.com/11749936/.
When I check the nameservers on my other machines i get the DNS-IP of my router which is 127.*.*.* .

Is the primary problem connected to the one from the interactive troubleshooting? any ideas?
Thanks
akrea

It appears the DNS server on the HDA is not working properly.

Recommend you try switching it from OpenDNS to Google, then back following the Changing your DNS provider guidance.

I have seen in the past where that sometimes helps unwedge things.

Thanks bigfoot
Your hint led me to the idea of turning on the hda DNS even with the potential of conflicting with the existing DNS. But it worked an solved the problem. Yet I may need additional help on the DLNA. But I will start a separate thread on that one if needed.
Again thanks for your help!

Glad to hear it's working now. No need to turn off DNS on HDA. It will not affect the network unless you use the HDA for DHCP server capability.