Re: DNS and internet
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Tue, 17 Nov 2009 13:49:05 -0600
On 17 Nov 2009, in the Usenet newsgroup alt.os.linux.redhat, in article
<4b025057$0$18580$426a34cc@xxxxxxxxxxxx>, Steve wrote:
Moe Trin wrote:
The DNS-HOWTO is rather old, but will get you started. For additional
help with sub-domains (a.k.a. child domains), you probably want to be
reading the 'cricket book' (DNS and BIND) from O'Reilly and Assoc.
DNS and BIND, Fifth Edition May 2006 $49.99 ISBN: 978-0-596-10057-5
or 0-596-10057-4, 648 pages
I have a fix IP Address and up to know, I had enough with 5 subdomain
that my NIC provider gave me.
Unfortunately, I need to buy another domain (.fr)that my current
provider doesn't offer -> I changed for another one and this one,
doesn't allow me to do anything. ( in this case, I need to defined 2
differents address for the web and FTP server. If I want to do this,
the provider is offering me a package much more expensive... that I
don't need.
Are we talking about the same thing? A sub-domain is a domain within
the parent - such as
county.TLD parent domain
host.county.TLD host within parent domain
host2.county.TLD another host within parent domain
city.county.TLD child domain
host.city.county.TLD host within child domain
host2.city.county.TLD another host within child domain
street.city.country.TLD child domain within child domain
number.street.city.country.TLD host within that (sub-)sub-domain
Just as "country.TLD" could be a CNAME for a host in the parent
domain, you could also have "city.county.TLD" as a host name, but it
would have to be a CNAME within the child, and this can get rather
complicated to set up safely.
Your description here sounds more as if you have two (or more) domains
on the same physical host - which is a completely different problem.
That's just a number of extra zonefiles listed in /etc/named.conf
(although the PTR records can be ``interesting'').
Effectively, my problem is the second DNS ( the slave), which is not
defined yet. So if I have a crash..... I will see that later on.
When we first set up DNS in the 1980s, we had master and slave
located in the same room, on the same DMZ subnet, connected to the
world by the same router... which really wasn't as big a problem
as all of our network was reachable through a single T-1 only. If
it went down, you couldn't reach our DNS, but you also could not
reach any of our hosts, so it didn't matter that much (except for
inbound mail which still worked if the sender knew the MX addresses,
but not if they had to look those up first). By about 1988, we
changed things such that we had connections to the world through
several providers around the world, and had an internal set of links
to connect everything. This allowed us to put the master in one
facility, and the (three) slaves in three other facilities and each
had a "different" connection to the world. Each facility was also a
separate sub-domain (location.company.TLD), and each had their own
master/slave DNS servers (hostname.location.company.TLD) that are
authoritative for "their" sub-domain. Admining the individual
sub-domains and the company domain isn't that difficult, but I
certainly would not want to try to set it up without help and a lot
of reading of the 'cricket book'. ;-)
Old guy
.
- Follow-Ups:
- Re: DNS and internet
- From: Jacob
- Re: DNS and internet
- References:
- DNS and internet
- From: Steve
- Re: DNS and internet
- From: Jacob
- Re: DNS and internet
- From: Moe Trin
- Re: DNS and internet
- From: Steve
- DNS and internet
- Prev by Date: Re: DNS and internet
- Next by Date: Re: DNS and internet
- Previous by thread: Re: DNS and internet
- Next by thread: Re: DNS and internet
- Index(es):
Relevant Pages
|