[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Re: Primary/Secondary DNS on RaQ3



On Tue, 30 May 2000, Jay Tingley so wrote:

} Ignoring the slight, Brent, it was (and is) very noble of you to
} offer this, and I hope they take you up on that. The question was
} whether they could (yes), and how they would go about doing it
} (fairly easily) - not whether it shouldn't be done.

	Actually Jay, I believe you made the point better than I
ever could. Sometimes we miss the basic simplicities of things -
people who only have one domain running on their Cobalt can team up
with someone else who only has one domain on their Cobalt. While
organizations like Granite Canyon enter into the equation and are
worthy of consideration, one should not ignore the fact that once a
domain is delegated to a server anyone who can submit zone files to
that server can use the domain, with Granite Canyon that pretty
effectively means that the whole connected world can free load off
an unsuspecting user - perhaps even causing them legal problems in
the event they send UCE or Child Porn or some such thing.

	But this list is a vast resource of people who use the same
equipment and who more than likely have many many equals who would
be more than happy to swap DNS service with them. 

	All I'm suggesting is that the best way may be the required
way and that doing it is well within the reach of everyone on this
list.

	And doing this is very easy. Assuming a domain or two, tt's
a simple matter of including the zone files for which one is
providing secondary DNS service in their named.conf file - with a
few minor modifications: "master" has to be changed to slave and the
IP address of the zone's primary DNS server needs to be
included. Other than restarting named, that's it. Truth be told,
it's easier than setting up a second named is - a lot easier.

Primary (change this)   

	zone "foo.com" in {
		type master;
		file "db.foo";
        };

(to this) for Secondary and add it to named.conf 

	zone "foo.com" in {
		type slave;
		file "db.foo";
		masters { xxx.xxx.xxx.xxx; };
	}
	
	Then restart Bind and you're done.

	With lots of domains just create a named.conf for the
secondary zones and include it in your named.conf:

	include "/path/to/other/named.conf

	Peace be with you,
	
	Brent
	
	Brent Sims
	WebOkay Internet Services
	http://www.WebOkay.net
	Brent@xxxxxxxxxxx
	(719) 595-1427 (Voice/Fax)