I am working with a client and the question arose about if this could be
done:
Clients FTP data to one of two hosts.
If one host is down they actually update the DNS server entry to point the
down host to the other (backup) hostname
Is there a way to setup the DNS so that both host ip addresses a
What you describe is easy to do and is common practice for some
network services.
Even without a "load balancer", you can have hostname "www" point to
two different machines. I would do it with multiple A records in the
DNS. Protocols like HTTP carry out a complete transaction nicely that
way.
@VM.MARIST.EDU
Subject: Networking Question
I am working with a client and the question arose about if this could be
done:
Clients FTP data to one of two hosts.
If one host is down they actually update the DNS server entry to point the
down host to the other (backup) hostname
Is there a way to setup the DNS
On Friday, 06/10/2011 at 04:23 EDT, Lionel Dyck/Oakland/IBM@IBMUS wrote:
> Is there a way to setup the DNS so that both host ip addresses are
defined
> for a single hostname?
Yes [see Rick's post], but that likely isn't going to do what you want.
Most end-user client applications are simplistic,
trib...@garlic.com (Personal)
http://www.almaden.ibm.com/cs/people/triblet
Linux on 390 Port wrote on 06/10/2011 02:08:37
PM:
> From: Alan Altmark/Endicott/IBM@IBMUS
> To: LINUX-390@vm.marist.edu
> Date: 06/10/2011 02:13 PM
> Subject: Re: Networking Question
> Sent by: Linux on 390 Port
Hope this helps. Let me know if you have any questions.
Erik
> _
> From: Nix, Robert P.
> Sent: Tuesday, December 20, 2005 8:05 AM
> To: Barber, Erik A.; Piotrowicz, Ronald J.; 'Linux on 390 Port'
> Subject: N
Bob, why is the MTU size 1800?
> _
> From: Nix, Robert P.
> Sent: Tuesday, December 20, 2005 8:05 AM
> To: Barber, Erik A.; Piotrowicz, Ronald J.; 'Linux on 390 Port'
> Subject: Networking question after Saturday&
390 Port
<[EMAIL PROTECTED] Subject
ist.edu> Re: Networking question after
Saturday's upgrade attempt... With
pictures
From the symptoms, most likely your problem is in the external router
network. Packets were not able to get back to the Linux guests from the
corporate intranet. It is not enough to have the correct default routes
to get out to the network. The network must also have routes to get back.
Harold
