[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Additional Nameservers
- Subject: Re: [cobalt-users] Additional Nameservers
- From: "Gregory Ogorek" <greg@xxxxxxxxxxxxxx>
- Date: Fri Jul 27 09:36:30 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
I've setup virtual name servers on two Qube 2 servers. Here's the steps
Create a script in /root called check_eth0:1
Here's the script:
#!/usr/bin/perl
$x=`/sbin/ifconfig -a | /bin/egrep '^eth0:1' | /bin/awk '{print $1}'`;
if ($x =~ eth0){
exit 1;
} else {
$x = `/sbin/ifconfig eth0:1 VIRT-IPADDRESS netmask 255.255.255.0 up`;
open (MAIL, "|/bin/mail -s 'Fixed eth0:1' admin\@yourdomain.com <
/dev/null");
print MAIL "VIRT NS should be better now.\n";
close(MAIL);
}
# End Script
This should work on a Qube 3 also. I'm about to test it this weekend.
Then I edit the pri.domain.com file to point to the proper SOA
Then I restart named (/etc/rc.d/init.d/named stop then start)
The secondary Qube 2 name server is modified using the GUI and points to the
primary virt ip address. The secondary server grabs the changes when those
changes are saved to the server.
With the Qube 3, I believe I would only have to use the script above and
then use the GUI to build the zone files, since the new GUI supports SOA.
I've also upgraded the Qube 2 with RaQ 3 dns GUI templates and scripts. So
it has more functionality than the original, just not support for SOA.
This isn't perfect, but it has allowed us to run one set of Qube 2 servers
as our name servers while supporting resold hosting plans with their own
name server names.
GregO
----- Original Message -----
From: <baltimoremd@xxxxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Friday, July 27, 2001 6:37 PM
Subject: Re: [cobalt-users] Additional Nameservers
> On Thu, 26 Jul 2001, R. Hamburg wrote:
>
> >
> > > I've been asked by a customer to create nameservers on my system for
him,
> >
> > I had the same question some time ago. Not sure what system you use
however.
In a goggle search I found the folowing
Setting up Additional Virtual DNS Servers
It is possible to set-up a Virtual DNS server for each
unique IP on the server (you can have more
than one VDNS set on the server). To create ns1 and
ns2.seconddomain.com (and on) Virtual
DNS servers, follow these steps.
1.Add the domain, per the instructions above, to DNS.
Also, add ns1 and ns2 forward and
reverse records, using two unique IPs (not used for any
other VDNS).
2.Change SOA configuration to use ns1 and
ns2.seconddomain.com as nameservers for
seconddomain.com. Also change it that way for any other
domains that will be using it (e.g.
ns1 and ns2.seconddomain.com would be the nameservers
for thirddomain.com as well, if it
was to use ns1 and ns2.seconddomain.com); you must do
this for any and all domains that
will be using that VDNS set as their nameservers.
3.Ensure that the IPs you are using for VDNS hosts are
first set-up as virtual web sites.
Otherwise, the IP will not be reachable: it must be
first set-up as a virtual site in order to be
"up."
The question now is:
Is there anyway other than creating more virtual sites to have the new set
ip IP addresses "up" and reachable ?
Thom
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users