Frequently asked questions
What is DynConD?
DynConD is a client-side Global Server Load Balancer. DynConD is a DNS-based client-server network service for optimal server selection on the client-side, which takes into account the network distance between client and servers and the parameters of the server: service response time and/or server load
What are the benefits of DynConD?
- For clients: faster network service response time and faster data transfer, hence higher customer satisfaction with the network service
- For network service providers: Improved solution in case of server unavailability, improved management of server and Internet connection load, DDoS protection
- For basic network infrastructure/ISP’s: faster data throughput and reduced possibility of network congestion
- Global benefits: „green” use of IT resources by reducing the energy consumption of clients, servers and infrastructure
Who can use DynConD?
DynConD is useful for a variety of desktop or mobile apps and applications: business, finance, education, government, health, social networks, games, entertainment, advertising, information services, streaming services, real-time applications, database access, IoT, VR, web hosting, cloud computing, VPS...
How do I start using DynConD?
- Configure GSLB parameters on user portal
- Implement dyncondgetaddrinfo() function in client app (Android, Linux, iOS, Windows)
Can I use DynConD as a traditional server-side GSLB?
Yes, DynConD also has traditional GSLB functionality, by introducing support for a server-side composite DNS metric calculation. If DynConD is used as a traditional server-side GSLB, DynConD calculates the server-side composite DNS metric for A/AAAA RRs and returns A/AAAA RRs to the standard DNS client/resolver based on server availability, service response time and server load sorted from optimal to the less suitable. In this case DynConD library isn’t necessary on the client side so standard resolvers can be used. By using DynConD in this way, real-time network distance between client and server is not measured and no client-side server availability check is made by the DNS resolver.
Is geolocation used?
No, DynConD uses the measured network distance between client and server instead of the often imprecise geolocation
WIll I be notified if my servers go down?
Yes, with our new alerts notification system, you will always be aware of your server status - you will receive an email if your server goes down and a new one when the server goes up again.
How does the health checking work?
DynConD DNS client library performs real-time server availability checks, so unavailable servers are detected by the client during the DNS resolution process
Does DynConD work on Windows and Linux servers?
DynConD Agentless service response time measurement technology works for Windows and Linux hosted web services. DynConD Load client for server load measurement works on Windows and Linux servers
Do I still need a SLB/ADC?
No. By making the server IP addresses publicly available, DynConD will do the necessary load balancing on the user device since DynConD is a client-side load balancer
Can DynConD reduce latency?
Yes, by always selecting the optimal server, users will naturally always have the lowest possible latency
Is my data secure when I use DynConD?
By operating strictly on the Layer 3 and 4, DynConD doesn’t inspect or look into the content of the packets so all your data is perfectly secure
One of my servers just went down, what happens now?
DynConD client DNS library will detect unavailable servers during the network distance measurement phase and discard them
What can I configure in my server settings?
- Optimal server selection parameters: server response time impact, server load impact and service response time impact
- Parameters for RTT measurements on the client side: number of requests for network distance (server response time) measurement, number of msec between requests, protocol used for the network distance measurement, TCP port used for network distance measurement, time in msec from sending packets to declaring the server unavailable
- Other RR settings: A/AAAA RR TTL, TTL for TXT RR, Server Timeout, Number of RRs which DNS server sends to clients
Where can I configure my server settings?
You can configure your server settings on https://my.dyncond.com
How can I monitor my server load and service response time?
You can monitor the status of your servers on user portal:
- Graph and table data: https://my.dyncond.com/ServerGraph/ServerGraph
- Server real-time status: https://my.dyncond.com/ServerRTStatus/ServerRTStatus
I am using XYZ, how do I migrate to DynConD?
- Configure your FQDN and server settings on https://my.dyncond.com
- Change your A/AAAA/CNAME RR to point to your FQDN on dyncond.net GSLB DNS server
- Change your DNS resolving getaddrinfo() function with a new dyncondgetaddrinfo function (Linux, iOS) and/or InetAddress with a new DynConDInetAddress function (Android)
Can I use DynConD for Windows and Linux client applications?
Android, Linux, iOS and Windows client applications are supported.
Can I try out DynConD for free?
Yes, you can test DynConD free of charge for 30 days by signing up on the user portal.
Do I need to change something in my network service before using DynConD?
No changes are necessary, all you have to do is implement the DynConD library into your iOS and/or Android app and change your A/AAAA/CNAME RR to point to your FQDN on dyncond.net GSLB DNS server.
Which payment methods can I use?
PayPal as payment method is supported
Which Android and iOS versions does DynConD support?
All officially supported versions are supported, Android API level from 23 (Android 6.0 Marshmallow), iOS with no limitations.
What is DynConD Load Server?
DynConD Load Server is a part of the DynConD infrastructure responsible for the server load management by using a load agent for acquiring and delivering load parameters to the Load Server
What is DynConD Agentless server?
Agentless server is a proprietary DynConD technology for measuring the service response time
What is Dynamic Server Selection (DSS)?
Dynamic Server Selection is a new DNS method for optimal server selection for multiple available network services on a client side. DSS is based on a measured network distance between client and servers (in contrast to commonly used imprecise geographic proximity) and current server load or service response time
Does DynConD offer technical support?
Yes, technical support is included in the monthly subscription fee. You can contact us over social media, email us at or leave a message on the website
Will I have to update my app every time I add a new server?
No, all changes regarding servers are made only on the user portal
How long after adding new servers are they available to my users?
A new added server is immediately available to the users if an authoritative query to your FQDN on dyncond.net domain is performed, if a recursive query is used it depends on the configured RR TTL value
Can I block certain IP addresses?
By using impact factors some IP addresses can be favored over others
Can I influence the parameters of the server selection?
Yes, you can always adapt the server selection to your needs
Will DynConD receive patches and updates?
DynConD is always evolving and we are always looking to improve the user experience and satisfaction with small updates, tweaks and features
What is the difference between DynConD and a regular GSLB?
DynConD only needs one DNS lookup. No need for apps to perform an additional DNS lookup, only one DNS lookup is performed by the client for IP resolution, server availability check and optimal server selection. The final selection is performed on the client side, based on a measured network distance between client and servers (in contrast to commonly used imprecise geographic proximity) and current server load or service response time