Tinus Nijmeijers wrote:
just wanted to run this by some people more knowledgeable than myself.
please tell me if I'm wrong.
-at the registrar: change the IP of dns0.domain.net to the IP of NEW
-change the zone files on OLD and NEW to reflect the move to the new IP
-wait a couple of days for
You've got mismatched subnets. It might work with some hacking, but
you're better off designing it correctly.
Does the Linux box route? If not, you'll need to have a common subnet
at least from the Cisco router to Radio1, and you should insert a hub or
switch to tie together the data path
You've got mismatched subnets. It might work with some hacking, but
you're better off designing it correctly.
Does the Linux box route? If not, you'll need to have a common subnet
at least from the Cisco router to Radio1, and you should insert a hub or
switch to tie together the data path
I've added comments inline...
Rhesa Rozendaal wrote:
We are going to physically move our boxes, but for the dns the process
will amount to the same thing.
So here is what we'll do:
- Lower the ttl on all zones three days before the move
Lower the TTL on all zones OR INDIVIDUAL A RECORDS at least
I've added comments inline...
Rhesa Rozendaal wrote:
We are going to physically move our boxes, but for the dns the process
will amount to the same thing.
So here is what we'll do:
- Lower the ttl on all zones three days before the move
Lower the TTL on all zones OR INDIVIDUAL A RECORDS at least
aCaB wrote:
First off, ISP-B should be dropping your spoofed packets on the floor
once they hit their network.
I'm a strange guy, I know, but I totally disagree. IMHO An ISP should
provide a customer with the internet. That's it.
Right, that's it. The ISP should provide the Internet with the
aCaB wrote:
First off, ISP-B should be dropping your spoofed packets on the floor
once they hit their network.
I'm a strange guy, I know, but I totally disagree. IMHO An ISP should
provide a customer with the internet. That's it.
Right, that's it. The ISP should provide the Internet with the
Any ideas why the following won't actually send email when run from cron:
#!/usr/bin/perl
#
open(SENDMAIL,|sendmail $recipient);
print SENDMAIL From: WVFD EMS Dispatch [EMAIL PROTECTED]\n;
print SENDMAIL To: WVFD EMT $recipient\n;
print SENDMAIL Subject: Possible EMS call\n;
print SENDMAIL \n;
Any suggestions as to what might be causing this? It's a debian 1.3
system (I know, I know).
Jun 24 14:04:33 cs2 kernel: RPC: rpc_doio sending evil packet:
Jun 24 14:04:33 cs2 kernel: a1c8d23e 0100
0100
Jun 24 14:04:33 cs2 kernel:
On Fri, 5 May 2000, Adam Cassar wrote:
Maybe I should explain myself a little bit clear. The company I work for
has approx 1 zone files, with between 10-500 being delegated to our
servers each day.
Wow.
I was looking for a dynamic way to add a zone file to the server without
On Sat, 26 Feb 2000, Ken wrote:
Certain providers (e.g. Sprintlink and Digex) reportedly filter anything
smaller that /18 from non customers. I think these outfits do advertise
/24's for customers.
Almost all of them now filter longer than /24.
Pete
--
Peter J. Templin, Jr., CCNA
On Sun, 27 Feb 2000, t s a d i wrote:
ive always wanted to learn how stuff like dynamic routing really
works, and also, BGP ...
can anyone suggest to me a site that I can go to where I may find
those kinds of info ? (aside from cisco.com)
Well, Cisco's website is quite dry, but it's
12 matches
Mail list logo
