[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Crashed my ISP's DNS servers Ops (Please help)
- Subject: Re: [cobalt-users] Crashed my ISP's DNS servers Ops (Please help)
- From: Chris Bell <chris@xxxxxxxxxxxxxxx>
- Date: Fri Jan 25 23:51:19 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
At 09:58 PM 25/01/2002 -0800, you wrote:
I read an article on Interliant.com and added the following to
above Site Management:
ns1.enigmabiz.com 65.170.79.2
ns2.enigmabiz.com 65.170.79.3
I think possibly because the IP addresses you were given for use with your
Raq are in the same Class C or range as the ones they're using for their
DNS servers, when you added these sites your machine probably told the
network that you owned these IPs and... yeh whatever it's really their
fault for not anticipating that it would eventually happen. Just don't use
their IP addresses on your machine and that problem goes away.
I'm not sure what you're doing - looks like you've tried to set up the
above name server aliases by creating sites on your machine. They're not
sites though, they're just host names that should be configured in your
DNS. There's basically three things you need to do to get a site running on
a Raq:
1. Configure DNS servers (i.e. machines that run BIND) to host your domain.
Your hosting provider probably provides this for you on their servers,
although you can actually run BIND on your own machine as well. Avoid that
if possible. I have a control panel which allows me to configure DNS on my
provider's name servers. By configuring DNS you're telling other machines
on the Internet where to send requests for your web page, where to send
your mail etc. E.g. you tell your DNS that www.enigmabiz.com points to
65.170.79.187 (one of the IPs they gave you).
2. Register and delegate the domain. This points your domain to the name
servers you're using so that other machines know where to look for the
information configured in Step 1. This takes a while to kick in.
3. Configure a site on your Raq in the Site Manager - using a host name
(www), domain name (enigmabiz.com) and the IP address you set in the DNS
settings above.
It is quite possible that you have two IPs because your provider expects
you to run your own DNS servers. In this case you need to register two host
names with netsol.com and various other registrant bodies. Your host names
would be ns1.enigmabiz.com and ns2.enigmabiz.com, and each has to have a
_unique_ IP address (which is why you need 2). In other words you can't
register ns1.enigmabiz.com to 65.170.79.2 because your provider has already
registered the host name of their own DNS server to that IP address. If you
did that it would have a similar effect to the other problem you had
(although it would be quite hard to do).
Anyway avoid all that wherever possible.
It seems to me that you've made these configurations:
ns1.enigmabiz.com 65.170.79.2
ns2.enigmabiz.com 65.170.79.3
in your Site Manager rather than in your DNS settings (Step 1). If you want
to host your DNS on your provider's name servers, then you could configure
this in the DNS settings for the domain enigmabiz.com. After all, they're
just more hostnames, like www.enigmabiz.com and mail.enigmabiz.com.
The offshoot of that is that _most_ registrars will allow you to delegate
your domains to ns1.enigmabiz.com and ns2.enigmabiz.com, even though
they're really pointing to your provider's name servers.
Seems to me you don't have a very serious problem, so don't panic and get
some sleep - you just need to sort out your DNS hosting. I would recommend
asking your provider to configure DNS settings on their servers for you.
Then all you need to do is delegate your domains to their servers (Step 2)
and set up the sites using the Site Manager (Step 3).
Now back to trying to decide what to do about that rootkit...
cb