nothing wrong with running them both on the same server with seperate ip's for testing/learning purposes.
as for the cnames, these allow you point other names to existing a records.
so if you setup an A record for example.com, then when u try to resolve example.com then it will return the ip your set.
however, if you try to use something like
www.example.com, it wont resolve as you need to have each name setup seperatly.
so you can create a new A record for
www.example.com, or, use a cname, so instead of specifying the ip, you specify the name to point to.
so when you resolve
www.example.com, it checks its cname and returns the resolve for example.com.
also for your config, the files are actually split up seperatly.
the one u posted is the main conf file, this has the settings for the nameserver itself, and it defines each zone.
as the nameserver can be used any number of zones (domains) that you like.
the important one here is
Code:
zone "example.co.uk" {
type master;
file "/var/named/example.co.uk.hosts";
};
this creates a record for your domain "example.co.uk" and its a master server
then the next line, specifies the file for the config for that zone.
so if you look, u should have the file, /var/named/example.co.uk.hosts
in that file, u will find all the settings for your domain, like the ns records, a records, cname, etc.
also remember to setup an mx record if you plan to use the domain for mail as well.
have you setup your servers ip at ur domain provider so its pointing to your dns server ?
u can do a whois on the name to find out.
if your just doing it as a test internally, then u dont need to bother about that, thats for when u have ur own domain and want everyone to be able to resolve ur host
!
