Just being doing a load of DNSstuff.com queries to try and get everything to "pass", I noticed that some big players in the hosting scene have either open or closed DNS servers.
Softlayer.com have closed, while liquidweb.com are open...?
I have changed all mine to closed, just because dnsstuff advises it, but is there any reason you would want them open..?
Ive been learning alot about BIND and DNS, id like someone to check over what ive learn't to make sure my knowledge is correct.
A Zone:
A zone is basically 'similar' to a sub-domain but the domain google.com would not be a sub-domain, so a zone is not a sub-domain. In the domain google.com 'google' would be a deligated zone from the TLD 'com'. In another example: ny.google.com , 'ny' would be a zone for google's 'new york' department, if they had one.
Hosts:
The host name is usually the most left word in a domain or you can look at it as the leaves on an inverted tree in the DNS System. Examples:
www.google.com = 'www' would be the host
mail.sitepoint.com = 'mail' would be the host
ny.google.com = 'ny' would NOT be a host because its a 'zone' and does not offer a 'service' like ftp, mail, www ect. would. Unless 'ny' was intended to be a service then it would be a host, but it would have to become a leaf in the inverted tree, so you wouldn't ba able to create any zones from it like 'mail.ny.google.com' ... if that makes sense.
Nameservers:
If i used BIND on my server to manage my Zones and DNS information (which is pretty much standard), that would be my Nameserver. Its job would be to convert human recognizable names into computer recognizable names/numbers/ip.
My nameserver would only have authority over zones that are not deligated. So an example, 'com' deligate 'mydomainname' to me (mydomainname.com) they have no authority over that zone. So if i set up a nameserver on mydomain.com they have no authority over mydomainname or any zone under that.
Domain Namespace
The Domain Namespace was setup to replace the method used by ARPA (later DARPA) in the 60's in an effort to create a database of hosts that were easy to administer and reduced the time and server load on the old skool HOSTS.TXT method.
A domain namespace is a way to identify the different domains. Im not to good at explaining what i mean but basically ill illustrate this example:
google.com and google.net both have the same names, so the namespace in this example would the the TLD's 'net' and 'com' to seperate them.
Go a bit deeper for example:
cd.music.com and cd.disk.com , both have the same TLD and sub-domain's so the namespace here is the first-level domain 'music' and 'disk'.
Sub-Domains
Sub-Domains are similar to zones, in a way. A domain name: 'google.com' might have the sub-domain 'video.google.com' which links to the video section of google. 'video' is not a deligated zone from 'google' neither is it a host as such, so its a sub-domain.
Im probably slightly confused on some parts, and im open for comments. I dont fully understand alot of it, but what ive learnt so far took a good day to get my head around. If anythings wrong, id like to know.
Cpanel version 11.1.0
Fedora Core 6
This is a totally fresh install. I noticed bind was not running so I went to do a restart in WHM and I get the following error..
named has failed, please contact the sysadmin (result was "named is not running"). Jun 5 14:19:14 dts131 named: /etc/named.conf:65: open: /var/named/named.rfc1912.zones: file not found
I've got two domains (for sake of example, domain A and domain B). Domain A resolves correctly to my web server. Domain B is just sitting collecting dust. I didn't set these domains up, a previous programmer at my job did.
How do I configure resolv.conf, named.conf and the zone file(s) correctly to have domain B redirect to domain A?
I've already set up httpd.conf so that any requests for the host name of domain A will redirect.
e.g. [url]-> [url]
I just need the DNS part of this fixed (that I'm a bit of a noob at).
Do I have to do something like this in named.conf:
Code:
zone "domaina.com" {
type master;
file "/var/named/domaina.com.hosts";
};
zone "domainb.com" {
type master;
file "/var/named/domaina.com.hosts";
};
Then in the domaina.com.hosts zone file add an alias like this?
Code:
domainb.com. IN CNAME domaina.com.
Or do I need to create a domainb.com.hosts zone file with basic info emulating domaina.com.hosts zone file, and add its entry in named.conf?
I've got two domains (for sake of example, domain A and domain B). Domain A resolves correctly to my web server. Domain B is just sitting collecting dust. I didn't set these domains up, a previous programmer at my job did.
How do I configure resolv.conf, named.conf and the zone file(s) correctly to have domain B redirect to domain A?
I've already set up httpd.conf so that any requests for the host name of domain A will redirect.
e.g. [url]
I just need the DNS part of this fixed (that I'm a bit of a noob at).
Do I have to do something like this in named.conf:
Code:
zone "domaina.com" {
type master;
file "/var/named/domaina.com.hosts";
};
zone "domainb.com" {
type master;
file "/var/named/domaina.com.hosts";
};
Then in the domaina.com.hosts zone file add an alias like this?
Code:
domainb.com. IN CNAME domaina.com.
Or do I need to create a domainb.com.hosts zone file with basic info emulating domaina.com.hosts zone file, and add its entry in named.conf?