SOLVED: No DNS even on server itself

[cybercowboy]

I've been running Amahi 6 for a LONG time, and am trying to upgrade to 8 (not really relevant except to say/show I'm familiar with the setup/running of the server.)

I installed from the Fedora Minimal CD

I've set up my desktop to use a static IP address at 192.168.1.99 with name Firestorm

Server's address is 192.168.1.10

when I'm SSH'd into the server, if I ping 192.168.1.99 I get a response as expected.

When I ping 8.8.8.8 I get a response as expected

When I ping Firestorm I get:
ping: unknown host Firestorm


When I ping Google.com, I likewise get:
ping: unknown host google.com

DHCP/DNS are turned off in my router

my ifconfig reads as follows:

Code: Select all

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::5054:ff:fe68:2ff1 prefixlen 64 scopeid 0x20<link> ether 52:54:00:68:2f:f1 txqueuelen 1000 (Ethernet) RX packets 2350 bytes 501018 (489.2 KiB) RX errors 0 dropped 10 overruns 0 frame 0 TX packets 1038 bytes 272199 (265.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 1578 bytes 131820 (128.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1578 bytes 131820 (128.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 1a:a4:1b:8c:a0:7e txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

my /etc/resolv.conf is:

Code: Select all

# Automatically generated by hda-ctl on 2015-09-24 20:20:45 search Jamesganghome.net nameserver 192.168.1.10 nameserver 192.168.1.10

Am I correct in that instead of the second nameserver being the same as the first in my resolv.conf it should be one of the OpenDNS? If so how do i correct?

[bigfoot65]

Did you verify the DHCP and DNS server being used by your client?

Also if you want to change the DNS server, please use the UI and not command line.

Best not to mess with /etc/resolve.conf or you might cause other issues. There should be no command line required for the DNS server to work properly.

Have you installed any applications manually or modified any configuration files since the initial install?

EDIT: Please provide the URL from the following:

Code: Select all

fpaste --sysinfo

[cybercowboy]

Did you verify the DHCP and DNS server being used by your client?

Yes, but the failed pings above are from the server itself, NOT the desktop/client, so at least the google one should have worked even if the client didn't.

Also if you want to change the DNS server, please use the UI and not command line.

Best not to mess with /etc/resolve.conf or you might cause other issues. There should be no command line required for the DNS server to work properly.

Yea I get that, I was just giving my resolv.conf file because it looked strange to me, I've not changed any config files from what was installed on the desktop.

Have you installed any applications manually or modified any configuration files since the initial install?

Only the "xfce desktop" group and net-tools

When I attempted the fpaste --sysinfo I get

Code: Select all

Error Uploading: [Errno -2] Name or service not known

which makes sense since the server isn't able to resolve anything out on the net.

Again I've used Amahi 6 for years, and while I usually use Debian based setups, I'm fairly proficient at least in the basics of Linux. as such I did make a change just now to resolv.conf by adding "nameserver 8.8.8.8" and then re-ran the "fpaste --sysinfo"
which gave me

Code: Select all

http://ur1.ca/nur1o -> http://paste.fedoraproject.org/271305/14431504

After which I went back into resolv.conf and removed the line I added.

[bigfoot65]

Only the "xfce desktop" group and net-tools

That's your problem. The installation of a desktop is known to break Amahi 8. See the Amahi 8 Troubleshooting wiki page.

This may or may not work for you. Sorry, but there is no other known solution at this time other than reinstall and not use a Desktop on the server. The VNC application is no longer available for Amahi 7/8 and we discourage installation of the Desktop on the HDA due to the complications.

We cannot provide support any longer for this sort of modification.

[cybercowboy]

ok, at least that's solved. Is at least the VNC issue going to be resolved, or is it viewed as a permanent "broken"? I know I'm probably in the minority but I rely on VPNing into the HDA and then running VNC on it pretty heavily and if that's not an option (And I can't get to another device on the HDA's network via VPN) I'll have to stick with 6. If the VPN had changed since 6 that I can VPN through the HDA to my desktop at home I can make it work though.

[cybercowboy]

On a completely unrelated note, Bigfoot, do you ever sleep, seems like regardless of when I post a question on here, within a few hours you've come up with a very helpful reply. I just want to say this forum has some of the best admin support of ANY project I've used or been involved in.

[bigfoot65]

Yes I do sleep, but not much LOL

Glad my advice is helpful. Sometimes I don't feel I do enough

As for the VNC, I do not anticipate it being supported whatsoever in Amahi 8. I do believe there is a way to access all your machines in your network though without it. There is some guidance on the OpenVPN wiki page that might help with your requirement.

[WiFiNetGuy]

I was looking over the threads because of a problem I was having since installing Amahi 8. I couldn't get DHCP and DNS to work and had to statically assign both to a computer on my network to get it to work. Anyway, I came across this thread. I, too, had installed VNC since I had it on v7. I didn't even look, I just installed it without reading the big, bold WARNING. LOL.

After reading this thread and Bigfoot's response about VNC being an issue with Amahi 8's networking, I went ahead and took a chance and simply uninstalled VNC on my box, then rebooted. After it came back up, both DHCP and DNS are working again. Of course, that could change without notice, but for now it's working like I expect.

Just wanted to relay my experience with this issue. Hope it helps someone else. I'll update if the status changes.

[cybercowboy]

WifiNetGuy,

I was able to find a fix that allowed me to use VNC along with Amahi's DHCP/DNS settings, I'll see if I can find the work around and if so I'll post it.

[cybercowboy]

Ah, the fix was right in BigFoot65's links: https://wiki.amahi.org/index.php/Amahi_ ... HCP_Server

I did the steps there after installing the desktop and VNC, has worked like a champ for a few months now.