Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Forward domain to multiple IPs

[miguelal]

Forward domain to multiple IPs

I have a domain setup on my Plesk 8.6.0 powered webserver which is being forwarded to a specific IP provided by my costumer, all DNS zone records are inserted accordingly and everything works fine.
Due to a problem with the ISP that provides the fixed IP on my costumer’s server he now wants to get a second IP from a different ISP, for the same webserver, to function as a secondary route onto his server.
Naturally he’s asking me to set it up on my server so traffic gets routed to the secondary IP in case the primary one fails.
How do I do this?
Any help is much appreciated.

[Jaseeey]

Have you tried registering a number of nameservers, each one according to each server. That way, if one fails, it tries the next.

[miguelal]

My webserver is primary and secondary nameserver to my costumer's domain.
I'm not sure I follow.

[Xous]

Hi,
This is generally not possible.
You would need assistance from the ISP you are borrowing the IP address from and probably the ISP hosting your web server.
This would also not provide any redundancy as the packets will still have to traverse the "web server" ISP's network.





__________________Need shared hosting? Go with a host that has been in the business for 15 years and still going strong.
Looking to sell a monitoring or DNS service?
Looking to sell hosting clients and/or entire hosting company? Shoot me a PM with contact details.

[Xous]

Quote:



Originally Posted by Jaseeey


Have you tried registering a number of nameservers, each one according to each server. That way, if one fails, it tries the next.


Your mistaken. DNS operates in a round robin fashion.
I.e if you have two name-servers (ns-a, ns-b) and you have two clients (client-a, client-b).
client-a's resolver (or their ISP's) will ask for the name-servers for example.net.
They will get both ns-a and ns-b.
The resolver will then choose ONE name-server and if that name-server is down resolution will fail.
It chooses ns-a and ns-a happens to be down.
It will not try ns-b. (the result MAY be cached.)
client-b's resolver (or their ISP's) asks for the name-servers for example.net.
They will get both ns-a and ns-b.
The resolver will then choose ONE name-server and if that name-server is down resolution will fail.
It chooses ns-b and although ns-a is down it does not affect ns-a.
Resolution succeeds. (The result will be cached)
It does not try ns-a.





__________________Need shared hosting? Go with a host that has been in the business for 15 years and still going strong.
Looking to sell a monitoring or DNS service?
Looking to sell hosting clients and/or entire hosting company? Shoot me a PM with contact details.

[plumsauce]

Round robin has exactly nothing to do with this situation.
Neither does whether ns1 or ns2 are down, since they are on other machines.
The solution is either:
1. a dns service that has failover monitoring.
2. one of the dyanmic dns services that can be controlled by scripts from the customer server.
The usual generic dns server setups will not work in this situation.
.





__________________█ server uptime monitor and alert service - basicstate.com█ MSNBC.COM - Site of the Week█ managed dns global failover and load balance - edgedirector.com