Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
Centralised Local DNS (view source)
Revision as of 03:11, 16 November 2012
, 03:11, 16 November 2012no edit summary
Amahi uses "Bind" for its DNS, and Bind looks to the file /etc/named.conf for DNS-related configurations. You'll see in there some stuff that Amahi is in control of (eg the "zone" used by your network, et "home.com"). At the very bottom, you should see an include to "/etc/named.conf.local". This is where our magic will start. Basically, as su (or sudo) you need to open up this file and place an entry like this:
{{CodeText|CodeText=zone "test.mydomainname.com" {
type master;
file "/etc/bind/test.mydomainname.com";
What this does is tell Bind that, for the domain "test.mydomainname.com", you want to go to the file "/etc/bind/test.mydomainname.com" to look up the configuration.
<b>NOTE: </b> Notice that there's a "test." prefix on the domain. This is so that the test server will be internal machine (ie wherever we are going to point it to in the above-mentioned conf file) without affecting how other subdomains of the same domain. So "www.mydomainname.com" will still go to the live website (if that's what you wanted!).
Right, now create the following folder: "/etc/bind/". In here, you can store all the config files for each "zone" you want to configure. Once you've done that, you can create the config file "/etc/bind/test.mydomainname.com". The contents of this should be like this:
{{CodeText|CodeText=$TTL 604800
@ IN SOA ns.test.mydomainname.com. test.mydomainname.com. (
1 ; Serial
