DNS not resolving / named.conf 2 locations?

[taylorfamily1994]

My dns is not resolving when I use my HDA as my DNS server (192.168.3.30) - This is a CLEAN install of both OS and Amahi.

The DNS *IS* running verified through both netstat -anop and looking at port :53 AND looking through the HDA control panel at servers (says both DNS and DNS updater are running).

After digging around I found that named.conf is located in BOTH root "/" and /etc. However, these 2 files are different.

named.conf located at / (root)
http://pastebin.com/b6JaVRzd

named.conf located at /etc/
http://pastebin.com/tUedEPEg

I think I either need to:
a.) Replace /etc/named.conf with /named.conf OR
b.) MERGE /etc/named.conf with /named.conf

Help?

[bigfoot65]

I would recommend you run the network troubleshooter.

http://wiki.amahi.org/index.php/Network_troubleshooting

DO NOT mess with the named.conf files as it could cause problems. There should not be one in / directory. I checked my HDA and only one exists. Did you do some modifications to the HDA? Maybe the one located in / is causing problems.

[taylorfamily1994]

Look, I understand named.conf files (and conf files in general) for most part and I could probably figure out what needs to be included in the /etc/named.conf file myself.

I was *hopeful* that someone with more experience than I on this particular subject could chime in and tell me if I can just replace /etc/named.conf with /named.conf or if I need to merge.
I believe I need to merge them as some of the settings are different.

I have ipv6 disabled on my network and I'm wondering if that might have caused this to drop this particular named.conf file in the root directory when it was trying to find the ipv6 information. A variable was probably null that it was expecting to be set.

Just a hunch.

[bigfoot65]

Ok. There is no need for the snippy reply. As a community, we all try to help but may not have the right answers. The point here is we are offering advice/recommendations based on our experiences. So if we are incorrect, it is not intentional.

Maybe someone else with more experience will be able to assist with your problem.

[taylorfamily1994]

I was actually going for sardonic....

Telling some of us to not mess with conf files is like telling someone not to touch a hot burner because they might get burned. It should go with a caveat like [unless you are comfortable rebuilding your server] etc.

But, point taken - I'll try to be more gracious in the future.

[bigfoot65]

Understand. I will remember next time not to be so aggressive with my comments. My intentions were good, just not as well received

Thanks for the feedback.

[radioz]

Well, before messing with named.conf, what are your results from the network troubleshooter?

Did you turn off DNS in your router?

[taylorfamily1994]

Yes - DHCP is off (hence no DNS propogation to the clients) and DHCP/DNS was active on the HDA. The DNS configuration was really screwed up as the HDA itself could not resolve DNS lookups.

I rebuilt the Kernel and re-enabled IPV6 and wiped Amahi/httpd/mysql/bind/ruby from the server and reinstalled. I *had* to use the hda-new-install command to get it to work going this route but everything is working as it should now and the named.conf file is in the correct location now and seems to be configured correctly.

[radioz]

I'm glad you got it sorted out!