This is a discussion on Need advice for redundancy connections guidelines. within the Linux Networking forums, part of the Linux Forums category; I would like to have some servers and services available through different public IPs. I know how to distribute outgoing ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I would like to have some servers and services available through
different public IPs. I know how to distribute outgoing traffic from my server/services, but I'm in a bit of a mess with incomming one. Mainly I have doubts about DNS setup, since I have not time to study DNS in deepth. My main doubt is next: - Is it possible to manage public DNS servers (that's, DNS servers on "register.com" that I can manage just through a Web frontend) to distribute clients request through different IPs and setup some type of "fallback" if a public server/service IP is not available? - Could it be done in a general way or different patterns apply to different services (Web, Mail)? - What other possibilities appart from playing with DNS could be used (if any)? Thanks in advance for any help, hint or link. Enrique http://www.heraldodeinternet.com/Mem..._arizon_benito |
|
|||
|
On 27 Nov 2005, in the Usenet newsgroup comp.os.linux.networking, in article
<1133086836.345968.37920@o13g2000cwo.googlegroups. com>, enrique@heraldodeinternet.com wrote: >I would like to have some servers and services available through >different public IPs. I know how to distribute outgoing traffic from my >server/services, but I'm in a bit of a mess with incomming one. The term you are looking for is "round robin" - replying with a different answer (from a list) for each query. >Mainly I have doubts about DNS setup, since I have not time to study >DNS in deepth. DNS is most of it, but not all. >- Is it possible to manage public DNS servers (that's, DNS servers on >"register.com" that I can manage just through a Web frontend) to >distribute clients request through different IPs You'd have to discuss this with the organization running the DNS servers. >and setup some type of "fallback" if a public server/service IP is not >available? That's generally a client function - "try the next address if this one doesn't work". >- Could it be done in a general way or different patterns apply to >different services (Web, Mail)? Web - the same. Mail is rarely handled that way directly. You would use the preference values in the MX record. Should you really have that much mail activity that you really do have multiple severs at a given preference level, you could have the DNS servers round robin list them, but that's generally more hassle than it's worth. Old guy |
![]() |
| Thread Tools | |
| Display Modes | |
|
|