Secondary DNS server failure causes adminserver error

J

JaimeZepeda

New Member
Hello,

I am new here so I hope this is the right place for my question.

We experienced an adminserver error due to a failure in our secondary DNS server. We could not stop the adminserver or the name server properly. We noticed that our secondary DNS server had failed and we are certain that is the cause.

My question is why would the secondary DNS server cause a problem when the primary DNS server was still up?

Thanks for your input.

Jaime
 
What's your Progress/OpenEdge Version and what OS you're running on? Without giving more information it's almost impossible to say anything intelligent about what you're asking ...

Regards, RealHeavyDude.
 
Is it possible that the primary server is overwhelmed? I believe that secondary and tertiary servers are not just used in case of failure, but also when a response is not received quickly enough. If so, that would make a failed secondary a black hole, ready to be stepped in.
 
Thank you for the reply RealHeavyDude and tamhas.

The incident took place on an AIX host running OpenEdge 10.1B. I've not checekd with the network admin to determine the load on the primary DNS server at the time of the event. We do know that the secondary DNS failed (as in it shut down).

I'm culling through the OpenEdge documentation to learn how the DNS paramaters work in orer to understand why the secondary DNS failure caused the issue. I'll follow tamhas' suggestion regarding the load balancing between the DNS servers.

Jaime
 
I don't know that there is any load balancing possible. This may just be try #1, wait for a specified interval, if no answer try #2 ... and if #2 is down, then fail. The solution is to have a #3 so there is somewhere else to go.
 
You must log in or register to reply here.
Back
Top