View Single Post
  #1 (permalink)  
Old January 26th, 2005, 12:02 AM
gangu1971 gangu1971 is offline
Registered User
Points: 5, Level: 1
Points: 5, Level: 1 Points: 5, Level: 1 Points: 5, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jan 2005
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default secondary DNS vs. second primary DNS

Hi everybody,

I have 2 independent lines provided by 2 independent ISP's, running a "serwer" (DNS and HTTP) on both of them. Let's say the domain is "my-domain.com" so the servers would be like:

SERVER1 (let's say 213.180.132.201)
DNS dns1.my-domain.com
HTTP www.my-domain.com

SERVER2 (let's say 209.202.216.26)
DNS dns2.my-domain.com
HTTP ww2.my-domain.com

dns1 is primary DNS server and dns2 is secondary.

www and ww2 servers the same service (actually run by the third machine, hidden form the net), so no matter if somebody types "www.my-domain.com" or "ww2.my-domain.com" he/she gets the same.

Under normal circumstances, if somebody types "www.my-domain.com" in his/her browser he/she is servered by SERVER1 - nothing strange. But, in case SERVER1 is down for some season, secondary DNS on the SERVER2 is still running and ... resolves it into 213.180.132.201 which is DOWN.

How should I set-up the secondary DNS so it resolves "www.my-domain.com" into "ww2.my-domain.com" or "209.202.216.26" in case SERVER1 is not operating properly? Or, maybe should I have also primary DNS on SERVER2?

P.
Reply With Quote