SRV Records

: Hosting Glossary; Disk Space; Hepsia Control Panel; Hosted Domains; InnoDB; Integrated Ticketing System; Email Accounts; Memcached; Node.js; Subdomains; Support; Data Traffic; Varnish; VPN Traffic; Assisted Website Migration; Weekly Backup; Order

An SRV record, which signifies Service record, is a DNS entry that is used to identify the servers which run a certain service for a domain. Put simply, you will be able to use your domain not only for a website, but also for an instant messaging server, a video streaming host or even a Voice-Over-IP server, for example, while you still have a website with it. Whenever you set up the SRV record, you can select what IP it will use, on which port the connection to the specific server is going to be established in addition to the priority and the weight of the record provided that there are several SRV records for the exact same service. The second option will enable you to employ different machines for load balancing and redundancy. With this kind of DNS records, you could use the same domain for various purposes and even with different providers in case the same one is unable to provide all services that you need.

SRV Records in Semi-dedicated Hosting

By using a semi-dedicated server plan from our company, you're going to be able to take advantage of our user-friendly DNS administration tool, that is a part of the in-house built Hepsia web hosting Control Panel. It's going to offer you a very simple interface to create a new record for each domain address hosted within the account, so if you wish to use a domain name for any purpose, you can set up a completely new SRV record with a few mouse clicks. Through basic text boxes, you'll need to type in the service, protocol and port number information, which you ought to have from the company providing you with the service. Furthermore, you are going to be able to pick what priority and weight the record will have if you intend to use a couple or more machines for the same service. The standard value for them is 10, but you could set any other value between 1 and 100 when necessary. Additionally, you'll have the option to adjust the TTL value from the standard 3600 seconds to any other value - thus setting the time this record is going to be live in the global DNS system after you remove it or edit it.