Back to Home

Best practices: split DNS (Split DNS) in 3CX Phone System infrastructure / 3CX Ltd. Blog

FQDN · Split DNS · auto-configuration · dns server · 3cx phone system

Best Practices: Split DNS (Split DNS) in 3CX Phone System Infrastructure

Introduction


For the correct operation of the 3CX Phone System, it is recommended to configure and use the so-called split DNS (Split DNS). Split DNS uniformly represents the network host names (FQDNs) in the internal and external networks. In other words, the 3CX Phone System server will be available on a private and public network under a single FQDN name. This approach provides several advantages:
  • provides uniform configuration of internal and external connections to the server
  • accelerates user re-registration when switching from internal to external network and vice versa
  • allows you to create the same configuration for internal and external users 3CXPhone
  • allows you to administer the system, view reports and listen to recordings of conversations, regardless of user location
  • allows you to specify a single auto-tuning URL in IP phones, regardless of their location

To successfully configure Split DNS, a number of conditions must be met:
  • creating a self-signed SSL certificate, or purchasing a trusted certificate from an accredited company
  • availability of a registered domain name at a domain registrar
  • the presence of a static IP address
  • Your internal network must have a DNS server running. It can be a DNS based on Windows Server or a DNS server implemented in a firewall.

It is recommended that you create Split DNS before installing the 3CX Phone System server.

Split DNS is created in two stages:
  1. Configure the DNS zone on the public DNS server at the registrar of your domain name - public FQDN name of the server 3CX Phone System
  2. A similar zone is created in the internal DNS north - the private FQDN name of the 3CX Phone System server

Public FQDN server name


We show the setting of the public name of the server using the example of the EuroDNS registrar. For other registrars, the procedure is not fundamentally different.
  1. Log in to your account.
  2. Go to Control Panel > Zone Profiles
    add zone provile - Copy
  3. Click Add Zone Profile
  4. Click Rename Zone Profile and name the profile. In this example, we used example.com . Click Rename to save the profile name.
  5. Click Add DNS Record and select A (IPv4 Address) from the menu.
    add a record
  6. In the Host field, specify the desired server name. In our example, this is pbx
  7. In the IP Address V4 field, specify the public IP address of your 3CX Phone System server
  8. TTL field leave default 3600
  9. To save the settings, press ✓. An A record (your FQDN server name) pbx.example.com will be created. After some time, which can take up to 24 hours , your public FQDN server name will be converted to a public IP address.

To test that the public FQDN name is configured correctly, at the command prompt, type nslookup pbx.example.com . The command must be executed on a computer located on the external network. In response, you should get the external IP address of the 3CX server.

Private FQDN server name


We show how to configure a private FQDN name on a DNS server located on your company's internal network. The example is based on the Windows 2012 R2 DNS server and assumes that the server is configured from scratch.

Enabling the DNS Role


add roles
  1. Launch Server Manager
  2. In the upper right corner of the Server Manager window, click Manage and select Add Roles and Features from the drop-down menu.
  3. In the Add Roles and Features Wizard window, click Next
  4. Leave the default option Role-based or feature-based installation and click Next.
  5. Select the server to which you want to assign a new role and click Next
  6. In the list, select DNS Server . In the dialog that appears, leave the default values, click Add Features and Next
  7. On the Features page, click Next.
  8. On the DNS Server page, click Next
  9. Click Install
  10. When installation is complete, click Close.

After adding the DNS server role, create a Split DNS zone and records in it.

Adding a New Zone



A new zone is created in the Server Manager snap-in:
  1. In the upper right corner of the snap-in, select Tools and in the DNS drop-down menu
  2. The DNS manager will open. Right-click on the server name and select New Zone ...
  3. In the New Zone Wizard, click Next
  4. Leave the default primary zone and click Next.
  5. Select Forward lookup zone and click Next.

  6. Enter the name of the zone, in our example, example.com , and click Next
  7. On the Zone File page, leave the default settings and click Next.
  8. On the Dynamic Update page, leave the default options, click Next and Finish

Adding a new host




The newly created zone will appear in the Forward Lookup Zones section:


  1. Right-click on the created zone and select New Host (A or AAAA) ...
  2. Specify the host name, in our example, pbx
  3. Specify the private (local) IP address of the 3CX Phone System server
  4. Click Add Host . A message appears stating that the pbx.example.com entry has been created. Click OK and Done

It is this FQDN name that you specify during the installation of the 3CX Phone System server in the FQDN section.

To test that the private FQDN name is configured correctly, at the command prompt, type nslookup pbx.example.com . The command must be executed on a computer located on the internal network. In response, you should get the internal IP address of the server.
Split DNS is created. From now on, the 3CX Phone System will use a single FQDN name on the public and private networks.

Possible problems


Depending on the type of DNS server used, you may find that your other hosts, for example, the web server www.example.com , become unavailable from the internal network. This is due to the fact that your local DNS server will begin to use the internal DNS zone, and not redirect requests from local clients to an external DNS server. In this case, it is necessary to duplicate in the internal DNS zone A records of all hosts located in the external DNS zone. A record must contain the domain name of the host and its public IP address.


Additional Information


Read Next