I have a primary and secondary dns server setup in resolv.conf, with a timeout option of 1 second.The idea is when the primary fails, my secondary server picks up the workload.When openser is running, and primary dns is down, I am seeing several re-transmissions of 200 OK (invite) to my originator *after* openser has finished processing ACK. I was thinking the final responses would stop reTX after the ACK was t_relayed. Have you seen such behavior? And better yet- Is there a solution for this?Thanks, Will
Will Quan wrote:
I have a primary and secondary dns server setup in resolv.conf, with a timeout option of 1 second.The idea is when the primary fails, my secondary server picks up the workload.When openser is running, and primary dns is down, I am seeing several re-transmissions of 200 OK (invite) to my originator *after* openser has finished processing ACK. I was thinking the final responses would stop reTX after the ACK was t_relayed. Have you seen such behavior? And better yet- Is there a solution for this?Thanks, Will
Are you sure this problem is related to DNS failover?
regards klaus
_______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Just a thought,
are these DNS servers external or internal DNS servers?
Your posts seems to imply that they are internal DNS servers on your network which you have control over. In which case it is worth checking that there is proper replication between the two DNS servers (i.e. all DNS to Host mappings relating to/pointing to your openser server exist and are identical on both DNS servers). In your situation I guess replication from primary to secondary DNS server in particular.
On 11/01/07, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Will Quan wrote:
I have a primary and secondary dns server setup in resolv.conf, with a timeout option of 1 second.The idea is when the primary fails, my secondary server picks up the workload.When openser is running, and primary dns is down, I am seeing several re-transmissions of 200 OK (invite) to my originator *after* openser has finished processing ACK. I was thinking the final responses would stop reTX after the ACK was t_relayed. Have you seen such behavior? And better yet- Is there a solution for this?Thanks, Will
Are you sure this problem is related to DNS failover?
regards klaus
_______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-- Klaus Darilion nic.at
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Will,
the 200 OK retransmission is done by the end client (UAS) and not by the proxy. Check if the ACK actually gets to the UAS. Maybe the change of DNS server changes the routing...
regards, bogdan
Will Quan wrote:
I have a primary and secondary dns server setup in resolv.conf, with a timeout option of 1 second. The idea is when the primary fails, my secondary server picks up the workload.
When openser is running, and primary dns is down, I am seeing several re-transmissions of 200 OK (invite) to my originator *after* openser has finished processing ACK. I was thinking the final responses would stop reTX after the ACK was t_relayed.
Have you seen such behavior? And better yet- Is there a solution for this? Thanks, Will
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Klaus Darilion -
Max Gregorian -
Will Quan