--- title: DNS & SRV Records Required for Geo-Redundant Setup description: In order to set up a geo-redundant configuration, it is necessary to create DNS A records and SRV records. This article outlines the specific A records and SRV records that will need to be created. --- [Skip to content](https://ukdocs.access4.com/dns-srv-records-required-for-geo-redundant-setup#main-content) [![Untitled design-3](https://ukdocs.access4.com/hs-fs/hubfs/Untitled%20design-3.png?width=300&height=60&name=Untitled%20design-3.png)](https://documentation.luminatewholesale.com/?hsLang=en) Open main navigation Close main navigation How Can We Help You? - There are no suggestions because the search field is empty. 1. [Access4 UK Knowledge Base](https://ukdocs.access4.com/?hsLang=en) 2. [VOIP & NETWORKING](https://ukdocs.access4.com/voip-networking?hsLang=en) 3. [Networking](https://ukdocs.access4.com/voip-networking?hsLang=en#networking) # DNS & SRV Records Required for Geo-Redundant Setup ## In order to set up a geo-redundant configuration, it is necessary to create DNS A records and SRV records. This article outlines the specific A records and SRV records that will need to be created. #### DNS A Records Assuming two Core servers with DNS A records of: | Name | | --- | | core1.acmecorp.com | | core2.acmecorp.com |   #### SRV Records Note the following when using this article: **TTL** means time to live.  **Priority v. Weight** We do not recommend changing weight for an SRV record because that will cause additional load on the server as it bounces traffic back and forth. Use priority instead. This still applies the load balancing concept, and still enables a failover, but it lessens the load on the server. ### SRV DNS Records for UDP Two new SRV DNS records for UDP Registrations: | # \_service.\_proto.name. | TTL | class | SRV | Priority | Weight | Port | Target | | --- | --- | --- | --- | --- | --- | --- | --- | | \_sip.\_udp.core1.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5080 | core1.acmecorp.com. | | \_sip.\_udp.core1.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5080 | core2.acmecorp.com. | | \_sip.\_udp.core2.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5080 | core2.acmecorp.com. | | \_sip.\_udp.core2.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5080 | core1.acmecorp.com. | ### SRV DNS Records for TCP Two new SRV DNS records for TCP Registrations: | # \_service.\_proto.name. | TTL | class | SRV | Priority | Weight | Port | Target | | --- | --- | --- | --- | --- | --- | --- | --- | | \_sip.\_tcp.core1.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5080 | core1.acmecorp.com. | | \_sip.\_tcp.core1.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5080 | core2.acmecorp.com. | | \_sip.\_tcp.core2.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5080 | core2.acmecorp.com. | | \_sip.\_tcp.core2.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5080 | core1.acmecorp.com. | ### SRV DNS Records for TLS Two new SRV DNS records for TLS Registrations: | # \_service.\_proto.name. | TTL | class | SRV | Priority | Weight | Port | Target | | --- | --- | --- | --- | --- | --- | --- | --- | | \_sip.\_tls.core1.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5082 | core1.acmecorp.com. | | \_sip.\_tls.core1.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5082 | core2.acmecorp.com. | | \_sip.\_tls.core2.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5082 | core2.acmecorp.com. | | \_sip.\_tls.core2.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5082 | core1.acmecorp.com. | Some devices use the \_sips service header with TLS instead of \_sip: | # \_service.\_proto.name. | TTL | class | SRV | Priority | Weight | Port | Target | | --- | --- | --- | --- | --- | --- | --- | --- | | \_sips.\_tls.core1.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5082 | core1.acmecorp.com. | | \_sips.\_tls.core1.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5082 | core2.acmecorp.com. | | \_sips.\_tls.core2.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5082 | core2.acmecorp.com. | | \_sips.\_tls.core2.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5082 | core1.acmecorp.com. | Some devices use the \_sips service header with TCP instead of \_sip: | # \_service.\_proto.name. | TTL | class | SRV | Priority | Weight | Port | Target | | --- | --- | --- | --- | --- | --- | --- | --- | | \_sips.\_tcp.core1.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5082 | core1.acmecorp.com. | | \_sips.\_tcp.core1.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5082 | core2.acmecorp.com. | | \_sips.\_tcp.core2.acmecorp.com. | 86400 | IN | SRV | 10 | 10 | 5082 | core2.acmecorp.com. | | \_sips.\_tcp.core2.acmecorp.com. | 86400 | IN | SRV | 20 | 10 | 5082 | core1.acmecorp.com. | - Reverse (***PTR*** records) DNS entries **MUST** be set for all servers. - ***SPF*** records must be set for all core servers. See your domain and email provider for more details Once you have completed all of these configuration steps you can check if this was done correctly using our SRV Checker that can be found at [https://devops.netsapiens.com/srvchecker/srvcheck2.php](https://devops.netsapiens.com/srvchecker/srvcheck2.php) #### Wildcard DNS Alias Records (OPTIONAL) Wildcard DNS alias records are only used for an older and deprecated redundancy method called dual-reg. This method is still supported but it was superseded by SRV Active/Active methods. Unless your systems are still using legacy devices with legacy configuration, it should not be needed and it is better to not configure it. If you will be configuring this option choose either two Wildcard CNAME or two Wildcard A records.  This may depend on what the DNS Server or Hosting Provider allows. | \*Name. | class | Record Type | Target | | --- | --- | --- | --- | | \*.core1.acmecorp.com. | IN | CNAME | core1.acmecorp.com. | | \*.core2.acmecorp.com. | IN | CNAME | core2.acmecorp.com. | - [Videos](https://ukdocs.access4.com/videos?hsLang=en#main-content) - [LMS](https://ukdocs.access4.com/videos?hsLang=en#lms) - [PBX](https://ukdocs.access4.com/pbx?hsLang=en#main-content) - [Auto Attendants](https://ukdocs.access4.com/pbx?hsLang=en#auto-attendants) - [Changelogs/Feature Releases](https://ukdocs.access4.com/pbx?hsLang=en#changelogs-feature-releases) - [Users](https://ukdocs.access4.com/pbx?hsLang=en#users) - [General](https://ukdocs.access4.com/pbx?hsLang=en#general) - [Phone Numbers](https://ukdocs.access4.com/pbx?hsLang=en#phone-numbers) - [Devices](https://ukdocs.access4.com/pbx?hsLang=en#devices) - [CDR & Call History](https://ukdocs.access4.com/pbx?hsLang=en#cdr-call-history) - [Voicemail](https://ukdocs.access4.com/pbx?hsLang=en#voicemail) - [Queues](https://ukdocs.access4.com/pbx?hsLang=en#queues) - [Answering Rules & Time Frames](https://ukdocs.access4.com/pbx?hsLang=en#answering-rules-time-frames) - [Domains](https://ukdocs.access4.com/pbx?hsLang=en#domains) - [FAQ](https://ukdocs.access4.com/pbx?hsLang=en#faq) - [APPLICATIONS](https://ukdocs.access4.com/applications?hsLang=en#main-content) - [Insights](https://ukdocs.access4.com/applications?hsLang=en#insights) - [Web App](https://ukdocs.access4.com/applications?hsLang=en#web-app) - [Mobile App](https://ukdocs.access4.com/applications?hsLang=en#mobile-app) - [HARDWARE](https://ukdocs.access4.com/hardware?hsLang=en#main-content) - [Snom](https://ukdocs.access4.com/hardware?hsLang=en#snom) - [Fanvil](https://ukdocs.access4.com/hardware?hsLang=en#fanvil) - [Grandstream](https://ukdocs.access4.com/hardware?hsLang=en#grandstream) - [General](https://ukdocs.access4.com/hardware?hsLang=en#general) - [Cisco](https://ukdocs.access4.com/hardware?hsLang=en#cisco) - [Polycom](https://ukdocs.access4.com/hardware?hsLang=en#polycom) - [Yealink](https://ukdocs.access4.com/hardware?hsLang=en#yealink) - [Avaya](https://ukdocs.access4.com/hardware?hsLang=en#avaya) - [VOIP & NETWORKING](https://ukdocs.access4.com/voip-networking?hsLang=en#main-content) - [VoIP](https://ukdocs.access4.com/voip-networking?hsLang=en#voip) - [Troubleshooting](https://ukdocs.access4.com/voip-networking?hsLang=en#troubleshooting) - [Routers](https://ukdocs.access4.com/voip-networking?hsLang=en#routers) - [Networking](https://ukdocs.access4.com/voip-networking?hsLang=en#networking) - [ADMIN](https://ukdocs.access4.com/admin?hsLang=en#main-content) - [Onboarding](https://ukdocs.access4.com/admin?hsLang=en#onboarding) - [Support](https://ukdocs.access4.com/admin?hsLang=en#support) - [Billing](https://ukdocs.access4.com/admin?hsLang=en#billing) - [PORTING & NUMBERING](https://ukdocs.access4.com/porting-numbering?hsLang=en#main-content) - [Number Management](https://ukdocs.access4.com/porting-numbering?hsLang=en#number-management) - [Porting](https://ukdocs.access4.com/porting-numbering?hsLang=en#porting) - [ADD ONS](https://ukdocs.access4.com/add-ons?hsLang=en#main-content) - [Vonage SMS](https://ukdocs.access4.com/add-ons?hsLang=en#vonage-sms) - [Teammate - Microsoft Teams Integration](https://ukdocs.access4.com/add-ons?hsLang=en#teammate-microsoft-teams-integration) - [CallCabinet - Advanced Call Recording Analytics](https://ukdocs.access4.com/add-ons?hsLang=en#callcabinet-advanced-call-recording-analytics) - [Datagate - Telecoms Billing Engine](https://ukdocs.access4.com/add-ons?hsLang=en#datagate-telecoms-billing-engine) - [Call Transcription & Sentiment Analysis](https://ukdocs.access4.com/add-ons?hsLang=en#call-transcription-sentiment-analysis) - [Nava - CRM Connector](https://ukdocs.access4.com/add-ons?hsLang=en#nava-crm-connector) - [PromptVoice - Professional Voice Recordings](https://ukdocs.access4.com/add-ons?hsLang=en#promptvoice-professional-voice-recordings) - [COMPLETE TRAINING](https://ukdocs.access4.com/complete-training?hsLang=en#main-content) - [Help Desk](https://ukdocs.access4.com/complete-training?hsLang=en#help-desk) [![Untitled design-3](https://ukdocs.access4.com/hs-fs/hubfs/Untitled%20design-3.png?width=100&height=20&name=Untitled%20design-3.png "Untitled design-3")](http://uk.access4.com) 1 Hardman St, Manchester M3 3EB Copyright © 2025 Access4 UK