Current Location :Home > About Us > News Center > BLOG > DNS SRV Failover in Practice: Does the Switch Actually Happen When the Resolver Stutters

DNS SRV Failover in Practice: Does the Switch Actually Happen When the Resolver Stutters

Nov 19Source:RedstoneIntelligent Browse: 2
Background

DNS SRV Failover in Practice: Does the Switch Actually Happen When the Resolver Stutters

A failover design is usually drawn as boxes and arrows, with a line running from the primary to the secondary. That line is DNS more often than not, and it is almost never reviewed with the same care as the boxes. A record set published with a long time to live, a resolver that caches aggressively, and a negative answer that sticks around are enough to turn a sound failover into a fifteen-minute outage that nobody can explain from the logs.

What a Service Record Actually Decides

A SIP client does not read a host name and pick an address. It asks for service records, receives a list of targets with priorities and weights, and then decides. Priority determines which group is used. Weight determines the order within a group. The important detail is that a client only moves to the lower-priority group when the higher-priority group is entirely unusable, and unusable is defined at the transport level. A target that resolves, answers, and then rejects the registration is not the same as a target that does not resolve at all.

DNS expresses preference, not health. A failover expressed only in DNS, and tested only by taking a name server down, has been tested against the one failure mode that DNS handles well. The failures that matter in practice are the ones where the primary resolves perfectly and simply will not take the registration.

StageExpected behaviourHow it fails
Service record lookupBoth priorities returnedOnly the primary group is published or cached
Address lookupAddress for the selected targetCached for longer than the service record TTL
Transport attemptRegistration acceptedTarget answers but refuses the registration
Negative answerRetried after the negative cache expiresSticks for the full negative caching period
Client re-registrationRetried on the configured intervalInterval longer than the recovery target

Timers Govern How Quickly a Change Is Seen

Two timers control this. The time to live on the service record bounds how long a resolver may reuse an answer. The negative caching timer bounds how long a resolver may reuse a no-such-record answer. Both are set in the zone, but many recursive resolvers apply their own minimums and their own behaviour, and some honour a short time to live on the service record while caching the address records beneath it for far longer.

Recovery time is therefore the sum of several timers nobody owns: the resolver cache, any intermediate cache between the site and the resolver, the client cache, and the re-registration interval on the device. A failover advertised as instantaneous can take minutes to take effect, and the gap between the advertised and the actual behaviour is where an incident gets escalated to a level it does not deserve.

Testing the Switch Rather Than Hoping for It

A failover test is only meaningful if you can observe both ends of the decision. Change the primary so that it stops accepting registrations, then watch what the client does: does it query for new records, does it receive the secondary, does it register there, and how long did each step take. Repeat the exercise with the primary returning an empty answer rather than a timeout, because an empty record set and a refused connection send the client down different paths.

Watch the resolver's own cache statistics during the exercise. A test that passes because the resolver happened to have been refreshed recently proves very little, and it will not reproduce during the incident it was supposed to prevent.

  • Publish the secondary in DNS, not only in a design document
  • Check the time to live on the address records as well as on the service records
  • Decide how negative answers will be cached and test that behaviour directly
  • Confirm the client re-registers on an interval consistent with your recovery target
  • Test both an empty answer and a refused connection; they behave differently
  • Record observed failover intervals and put them in the runbook
  • Keep a local resolver entry for the transport host so DNS is not the only path

Design Choices That Make Failover Real

Give the client something to choose between. A secondary that exists only in a slide is not a secondary. Keep the time to live consistent with how fast you can actually change the zone, since a short value combined with a manual update procedure just produces stale answers with a misleading expiry. Make sure the re-registration interval on the device fits the recovery time you are claiming, because no resolver will help a client that has not looked for a change yet.

Where the failure mode is name resolution itself, state the failover target as a fixed address on the device rather than a name. It is an inelegant answer and a completely reliable one when the resolver is the thing that has failed.

Redstone Approach

Redstone platforms support multiple SIP transport targets per trunk, with failover ordered by the platform as well as by name resolution, so the decision does not rest on resolver behaviour alone. Health-check status is reported per target and registration intervals are configurable, which makes a failover test observable during the exercise rather than inferred afterwards from an absence of complaints.

About Redstone

Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.


Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).


With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.


For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Contact Us

Mobile Phonel

Email: globalmarketing@redstonesystems.com

Address: 12816 SE 75th Court, Newcastle WA 98059, USA

Contact Us
We will do our best to contact you as soon as possible. In the meantime, please contact us for more information.
  • First Name*

  • Last name*

  • Company Name*

  • Email*

  • Phone

  • Product*

  • Message

  • I have read and agreed Privacy Policy
Privacy_policy
×

Privacy Statement

Platform information submission - privacy agreement

● Privacy Policy

We are committed to protecting the privacy, personal data and personal data (collectively referred to as "personal data") provided by you when using this website. Make us comply with the highest standards in terms of collection, use, storage and transmission of personal data (laws and regulations related to privacy of personal data) and consumer protection. To ensure that you have full confidence in the handling of personal data on this website, you must carefully read and understand the provisions of the privacy policy. This website (hereinafter referred to as "us") respects and protects the privacy of users. In particular, once you use this website, you will be deemed to accept, agree, promise and confirm this privacy agreement; You disclose your personal data to us voluntarily with the required consent; You will abide by any modification of this privacy policy; You agree that our relevant business personnel will contact you regarding the products and services you may be interested in (unless you have indicated that you do not want to receive such messages). With your consent, we will collect, manage and monitor the types of personal data collected


1. Scope of application

It is our unremitting pursuit to provide users with better, better and more personalized services. We also hope that the services we provide will be more convenient for your needs. This privacy policy applies to all information collection services provided by this website. You can visit this website and use the services provided by this website using this privacy policy


2. What information do we collect

In order to provide you with our various services, you need to provide personal data information, including personal data and anonymous data, including but not limited to: personal data (your name, gender, age, date of birth, telephone number, fax number, address or mailing address, e-mail address, etc.)


3. How to use the collected information

The purposes and purposes of collecting personal data and anonymous data are as follows: to provide you with our services through this website; When you use our website, you can identify and confirm your identity; Let you get the service for you when you use this website; The relevant business personnel of this website can contact you when necessary; Make it more convenient for you to use this website; The personal data and anonymous data provided by you to us will only be retained until the collection purpose has been achieved, unless they are retained due to applicable laws and regulations. The ownership of personal data and disclosure of all data collected on our website are owned by us and will not be leased or sold to any unrelated third party

 

4. How do we protect information

For the protection of personal data, we implement appropriate physical, electronic and management measures to protect and guarantee the safety of your personal data. We try our best to ensure that any personal data collected through this website is free from any nuisance of a third party unrelated to us. The security measures we take are not limited to: physical measures: the records with your personal data will be stored in a locked place Electronic measures: the computer data with your personal data will be stored in the computer system and storage media subject to strict login restrictions Management measures: only employees authorized by us can access your personal data, These employees need to comply with our internal rules on the confidentiality of personal data. If you are aware of any security loopholes on this website, please contact us in time so that we can take appropriate actions as soon as possible; Despite the implementation of the above security measures, we cannot guarantee the absolute security of data transmission on the Internet, so we cannot absolutely guarantee that the personal data and anonymous data you provide to us through this website are safe at all times. We will not be responsible for any unauthorized access to your personal data, and we will not be responsible for any losses and damages incurred or caused in this regard.

 

5. Juvenile Protection Law

The minor has provided personal data to this website without the approval or consent of any parent or guardian. Please contact the public telephone number and customer service telephone number on this website in time to ensure that the data are removed

 

6. Revision and effectiveness of privacy policy

With the expansion of the service scope of this website, we may revise the Legal Statement and Privacy Policy from time to time, which forms a part of this Legal Statement and Privacy Policy. In order to prevent you from being informed of such revisions, please read this Legal Statement and Privacy Policy frequently. In any way, if you continue to use our services, you agree to be bound by the revised Legal Statement and Privacy Policy