DNS and web server redondancy

  • Thread starter Thread starter PIerre
  • Start date Start date
P

PIerre

Hi, can you help my with this design:

Network 1:
- Internet provided by ISP 1
- Public IPs
- Firewall
- Primary Public DNS server 1
- Primary Public Web server 1

Network 2
- Internet provided by ISP 2
- Public IPs
- Firewall
- Public DNS 2
- Public Web Server 2

The two DNS server share the same 20 zones for the 20
domains name of my current clients. I have set the zone
transfert option.

The two Web server have replication 2 time each day
trought an VPN connection.

QUESTION:
- How do i set my DNS zone for hello.com to have 2 public
IP for the web server name www.hello.com. The point is if
i lost the internet connexion of the network 1, i will
lost my public DNS 1 and my public Web server 1 too.

Things to consider:
- The primairy Web server 1 is the most to date server
- If My DNS 1 server stop responding by my web server 1
is always online, my DNS 2 must give the web server 1 IP
to the client
- If my DNS1 AND my web server 1 stop responding, My DNS
2 must give the web server 2 IP
- If my Web server 1 stop responding but my DNS 1 is
running, the DNS1 must give the web server 2 IP

I dont know if iam clear, but ask if is not!

thank for your precious help!
 
Unfortunately, DNS does not help much here. You can add two A records for
the web server for sure. However, other DNS servers and clients will cache
the two addresses and use the first (unless net ordered) one first until
they TTL expire. What your looking for is a load balancer that will give
out A records based on load and server availability. I can't recommend any,
but someone here probably can.
--wjs
 
the problem for the load balancing is that my 2 server
are not at the same location. I can't use clustering or
load balancing rooters. I can't use round robin DNS
because RRDNS dos'nt check if the server is online...
 
the problem for the load balancing is that my 2 server
are not at the same location. I can't use clustering or
load balancing rooters.
Click to expand...
load balancing will still work even at different locations. You need a
product that can "ping" the different servers and/or run a client piece at
the server that talks to the load balancer/dns server. I have heard of such
products, but don't have hands on with them. Maybe someone can recommend
one?
I can't use round robin DNS
because RRDNS dos'nt check if the server is online...
Click to expand...
Correct. We agree.

--wjs
 
Back
Top