Hi Guys, we moved to a new house and thus I also had to move my HDA.
Booted fine, but for some reason local DNS is not resolving. Internet is working fine and I can only connect to shares and the HDA using the IP-address.
I went through the Network Troubleshooter and halted at step 4. tried to get answers in the IRC channel but was kickout twice from inactivity. So hope you can help me here. Its probably something simple.
heres the data I collected and shared in the IRC channel
https://paste.fedoraproject.org/paste/T ... 5A7wHdgZSg
SOLVED: Local DNS not working after moving my HDA
Re: Local DNS not working after moving my HDA
Did your network address change?
For example, if you go from 192.168.1.x to 192.168.2.x, there are changes that need to be made with your HDA.
There’s guidance in the wiki that describes how to make the change.
For example, if you go from 192.168.1.x to 192.168.2.x, there are changes that need to be made with your HDA.
There’s guidance in the wiki that describes how to make the change.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: Local DNS not working after moving my HDA
hi Bigfoot. no nothing changed. I only moved from one city to another, but even kept the same internet provider.
Re: Local DNS not working after moving my HDA
Odd that it's the same but not working.
Try switching the DNS provider in the dashboard from what you have currently to a different one. You can switch it back if you prefer a specific provider.
Sometimes that fixes the issue.
Otherwise, recommend you check out the Amahi 10 Troubleshooting page in the wiki.
There are a few things there that might help.
Try switching the DNS provider in the dashboard from what you have currently to a different one. You can switch it back if you prefer a specific provider.
Sometimes that fixes the issue.
Otherwise, recommend you check out the Amahi 10 Troubleshooting page in the wiki.
There are a few things there that might help.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: Local DNS not working after moving my HDA
I already tried that. Didnt help and externalDNS is working fine when browsing.
Problem is internal DNS for loca websites like transmission, Sabnzbdplus etc
My clients arent getting the correct DNS server from the DHCP server from the HDA
Problem is internal DNS for loca websites like transmission, Sabnzbdplus etc
My clients arent getting the correct DNS server from the DHCP server from the HDA
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : thuiz.com
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8260
Physical Address. . . . . . . . . : A4-34-D9-7D-D1-FB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:1c00:2a0a:7c00:85d9:d58:4af:9204(Preferred)
Temporary IPv6 Address. . . . . . : 2001:1c00:2a0a:7c00:2dad:ccf1:4956:c8dc(Deprecated)
Link-local IPv6 Address . . . . . : fe80::85d9:d58:4af:9204%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.178.151(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : vrijdag 5 juli 2019 23:00:31
Lease Expires . . . . . . . . . . : zaterdag 6 juli 2019 03:00:31
Default Gateway . . . . . . . . . : fe80::1a35:d1ff:fe0f:abc8%11
192.168.178.1
DHCP Server . . . . . . . . . . . : 192.168.178.12
DHCPv6 IAID . . . . . . . . . . . : 111424729
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-95-D3-BF-50-7B-9D-9C-17-25
DNS Servers . . . . . . . . . . . : 2001:b88:1002::10
2001:b88:1202::10
2001:730:3e42:1000::53
192.168.178.12
192.168.178.12
NetBIOS over Tcpip. . . . . . . . : Enabled
Re: Local DNS not working after moving my HDA
You might want to check log files for errors.
Would recommend you check the log in the apps directory for those you have issues with as well.
Would recommend you check the log in the apps directory for those you have issues with as well.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: Local DNS not working after moving my HDA
Ill do that. When I swapped DNS back and forth, it seemed to fix it for a day, next its back to the old problem and not resolving local DNS.
I'll check the log files and report back here.
I'll check the log files and report back here.
Re: Local DNS not working after moving my HDA
well I checked the log files, but cant really find any errors in them.
Where can I check out the DHCP configuration? BEcause it seems to put out DHCP leases with the wrong DNS server.
Where can I check out the DHCP configuration? BEcause it seems to put out DHCP leases with the wrong DNS server.
Re: Local DNS not working after moving my HDA
anybody? been 2 weeks since my last reply 

Re: Local DNS not working after moving my HDA
Forums are not very active these days. Most responses come from me.
I would suggest you check your Dashboard, Network tab, Settings section. What's in the dashboard is what Amahi incorporates automatically.
Have you check your client machines to ensure they receive the DNS automatically from the HDA? Some manually configure their clients to use a specific DNS. I presume you are using Amahi for DHCP and DNS so this should not be the cause.
DHCP and DNS is handled by dnsmasq. So if you look in /etc/dnsmasq.d/amahi-dns.conf and /etc/dnsmasq.d/amahi-dhcp.conf you should see the what clients along with IP addresses are being handed out. Note at the top of the amahi-dns.conf, you'll see the DNS servers based on Dashboard settings. In the /etc/dnsmasq.d/amahi-dhcp.conf it reflect the DHCP IP address range used.
I would suggest you check your Dashboard, Network tab, Settings section. What's in the dashboard is what Amahi incorporates automatically.
Have you check your client machines to ensure they receive the DNS automatically from the HDA? Some manually configure their clients to use a specific DNS. I presume you are using Amahi for DHCP and DNS so this should not be the cause.
DHCP and DNS is handled by dnsmasq. So if you look in /etc/dnsmasq.d/amahi-dns.conf and /etc/dnsmasq.d/amahi-dhcp.conf you should see the what clients along with IP addresses are being handed out. Note at the top of the amahi-dns.conf, you'll see the DNS servers based on Dashboard settings. In the /etc/dnsmasq.d/amahi-dhcp.conf it reflect the DHCP IP address range used.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Who is online
Users browsing this forum: No registered users and 2 guests