[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] New IP and old IP both work,
- Subject: Re: [cobalt-users] New IP and old IP both work,
- From: SteelHead <brk@xxxxxxxx>
- Date: Sun Jul 15 18:18:27 2001
- Organization: Linuxhelpers
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
----- Original Message -----
From: "Jim Scott" <cobaltlist@xxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Sunday, July 15, 2001 8:30 PM
Subject: Re: [cobalt-users] New IP and old IP both work,
> For one when changing the IP on these servers I have run into problems
with
> the old IP staying around bound to the ethernet card.
>
> Look at this file and take out the OLD ip if you find it there.
>
> /etc/sysconfig/network-scripts/ifcfg-eth0
it is not there but it does show up in ifcfg-eth0:0
DEVICE=eth0:0
IPADDR=OOO.OOO.OOO.OOO
NETMASK=255.255.255.0
NETWORK=OOO.OOO.OOO.AAA
BROADCAST=OOO.OOO.OOO.BBB
ONBOOT=yes
ALIAS=yes
BOOTPROTO=none
"ifcfg-eth0:0" 8 lines, 139 characters
Now my question is this, the file it resides in is, I expect, not needed.
the contents of the directory are here listed:
root@bluefish:/etc/sysconfig/network-scripts$ dir
ifcfg-eth0 ifdhcpc-done ifup ifup-sl
ifcfg-eth0.master ifdown ifup-plip network-functions
ifcfg-eth0:0 ifdown-post ifup-post
ifcfg-eth0:1 ifdown-ppp ifup-ppp
ifcfg-lo ifdown-sl ifup-routes
root@bluefish:/etc/sysconfig/network-scripts$
Which of these should remain, and which should be removed.
> Most likely it is still showing up.
>
> as for DNS do a dig on the DNS server you are using to resolve domains
with
> yourself and see what is shows for a record.
Right now I am not too concerned with the name issue, I know it will take
time to clear the name from the name servers. MY concern was moving this
box to a new ip due to hacking concerns. I just want to be sure it does not
respond to more than one ip.
> Assuming you have this utility.
>
> type dig ns @ns1.whateverdns.com www.whateverdomain.com
>
> this will cause the query to be performed on the DNS server of your
choice.
>
> Should show you the results and how long the record will take to expire.
>
> If you can provide me with more details I can probably help.
>
> Jim
>
Thanks Jim.
Bill
> ----- Original Message -----
> From: "SteelHead" <brk@xxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Sunday, July 15, 2001 7:15 PM
> Subject: [cobalt-users] New IP and old IP both work,
>
>
> > I changed the ip number on my RAQ1/2 and plugged it into a new port on
the
> > hub in a different segment. Ok, no big, the segment leaks and I can
> travel
> > between them to the new connection and old connection (different
> providers).
> >
> > What I am confused over is this little detail. I changed the IP# and I
am
> > able to connect to the new ip number. The box rebooted after the ip
> number
> > change even. I looked at control panel, and the new IP number is in
> place.
> >
> > I just pinged the name to see if the nameserver change happened, and it
> > pinged fine. Cool. except it is still pinging on the old IP number.
And
> on
> > the new IP number. I can ssh in on the old IP number and on the new IP
> > number. I need to reassign the ip number, so now I am at a loss.
> >
> > Can some enlightened person offer a reasaon for this confusion? I AM AT
A
> > TOTAL LOSS.
> >
> > Respectfully,
> > Bill
> >
> >
> > _______________________________________________
> > cobalt-users mailing list
> > cobalt-users@xxxxxxxxxxxxxxx
> > To Subscribe or Unsubscribe, please go to:
> > http://list.cobalt.com/mailman/listinfo/cobalt-users
> >
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>