Where can I find the DNS zone settings for my domain?
We provide free DNS service for all domains registered with us.
If you would like to use our DNS service for your domain, you can manage the DNS zone by following the steps below:
- Log in to our client area at client.syslock.hu.
- In the left-hand menu, select “Domains”, then “My Domains”.
- Click on the selected domain.
- On the domain details page, on the right-hand side, select “Cloudflare DNS”.
- If your domain is not yet connected to the Cloudflare service, please follow the instructions displayed there.
Using the Cloudflare DNS Manager in the Client Area
With the Cloudflare DNS Manager, you can manage your domain’s DNS settings directly from our client area. The interface allows you to view DNS records, add new records, edit and delete existing records, manage Cloudflare proxy status, and access certain optimization, caching, security, and analytics features.
If your domain is managed as a Cloudflare-connected zone through our service, you can modify the DNS records in the client area.
Main Menu Items
The following main menu items are available in the client-side interface: DNS Records, Optimization and Analytics, Logs. If the domain has not yet been activated under Cloudflare, a separate Cloudflare Protection view may also appear.
Cloudflare Protection
The Cloudflare Protection menu item may appear if the domain is not yet connected to the Cloudflare service. Here, the connection can be initiated using the Activate Cloudflare button. Once activation is complete, DNS record management and additional Cloudflare features will become available in the client area.
This step is usually required when the domain does not yet have a Cloudflare zone assigned to it, or the service has not yet been enabled for the domain.
DNS Records
Under the DNS Records menu item, you can view your domain’s current DNS entries. The list displays the record type, name, content, proxy status, and available actions, and a search field and filters are also available. This page also contains the Delete All Records and Add Record buttons.
DNS records determine which server, service, or mail handler the domain or subdomain points to. Each record type serves a different purpose, so before making changes, it is always recommended to check exactly which record you want to modify.
Search and Filtering
At the top of the record list, you will find a search field and filters. These allow you to quickly find the required entry by name, type, or proxy status. This is especially useful if the domain has many records.
Most Common Record Types at a Glance
The most commonly used record types are as follows:
- A record: points a hostname to an IPv4 address.
- AAAA record: points a hostname to an IPv6 address.
- CNAME record: points a hostname to another hostname.
- MX record: required for receiving email.
- TXT record: can be used for various text-based settings, such as authentication or verification.
Please note that A/AAAA records and CNAME records cannot exist at the same name at the same time, and an NS record also cannot exist together with another record type at the same name. For this reason, when creating a new record, the system may return an error if there is already a conflicting record under the specified name.
Adding a Record
You can create a new DNS entry using the Add Record button. Based on the public screenshot, the following fields appear in the interface: Type, Name (@ or www), IP Address, TTL and Proxy Status.
Field Descriptions
Type
Here you can select what type of DNS record you would like to create, such as an A, AAAA, or CNAME record. The available fields and required values may vary depending on the record type.
Name (@ or www)
This determines whether the record applies to the root domain or a subdomain. The @ symbol usually represents the root domain, while, for example, www represents the www subdomain.
IP Address / Content
This is the value of the record. Depending on the record type, it may be an IP address or another target value. For an A record, an IPv4 address must be provided, while for a CNAME record, a full hostname must be specified.
TTL
TTL determines how long DNS responses may be cached by querying servers. This also affects how quickly a change becomes visible to visitors. The Auto value usually means 300 seconds, and for proxied records this short TTL may be fixed.
Proxy Status
Here you can specify whether traffic for the given record should go directly to the target server or pass through the Cloudflare network. It is generally recommended to proxy A, AAAA, and CNAME records that serve web traffic, while records used for other purposes should not be proxied. Only A, AAAA, and CNAME records that serve HTTP or HTTPS traffic can be proxied.
When should Cloudflare proxy be enabled?
Enabling the Cloudflare proxy is generally recommended if the record serves a website or web application and you would like to take advantage of the benefits of the Cloudflare network, such as traffic routing and certain performance or security features.
For records related to email or used for domain verification purposes, proxying is generally not available and is not recommended. Records used for other purposes, such as CNAME records used for ownership verification, should not be proxied.
Editing a Record
To modify an existing record, click the Edit icon in the record’s row. This will open the record details, where the necessary changes can be made. Editing a record is done by opening the record, modifying the data, and then saving it.
After modifying a record, the change may not appear immediately everywhere. This is usually caused by TTL and DNS caching. With a shorter TTL, changes generally propagate more quickly.
Deleting a Record
If a record is no longer needed, it can be removed by clicking the Delete icon in the record’s row. Deletion may require confirmation, so please always make sure that you are removing the correct record.
Accidentally deleting a record may cause service disruption. This is especially true for websites, email services, or verification records, so it is recommended to make all changes carefully.
Deleting All Records
The Delete All Records button is used to remove records from the zone in bulk. Since this option may significantly affect the entire DNS zone, it is always recommended to verify beforehand whether deleting the full set of records is truly necessary. In the interface, this option appears as a separate, clearly visible action.
After using this function, web or email services connected to the domain may stop working until the required records are added again. For this reason, this option should only be used when justified.
Optimization
Under the Optimization menu item, three main functions are available: SSL/TLS Encryption, Cache Management, and Security Level.
SSL/TLS Encryption
The SSL/TLS Encryption setting controls how Cloudflare handles encryption between the visitor and Cloudflare, as well as between Cloudflare and the origin server. The Flexible mode encrypts only the connection between the visitor and Cloudflare, while Full and especially Full (Strict) provide more complete and secure end-to-end protection. Cloudflare specifically recommends using Full or Full (Strict) whenever possible.
As a general recommendation, it is advisable to choose a stronger encryption mode if a valid SSL certificate is also available on the hosting server. If you are unsure about the correct setting, please consult our support team before making any changes, as an incorrect SSL/TLS setting may cause accessibility issues.
Cache Management
Within the Cache Management section, the "Purge Everything" button is available. This action removes cached resources stored in Cloudflare’s data centers, and new requests will once again fetch the most up-to-date content from the origin server.
This can be useful if a website has been updated but visitors are still seeing old content. At the same time, after a full cache purge, the load on the origin server may temporarily increase because the content must be fetched again.
Security Level
The Security Level setting affects how strictly Cloudflare handles suspicious visitors and when it displays additional verification checks.
At a higher security level, more suspicious requests may be filtered out, but some legitimate visitors may also encounter verification. For this reason, this setting should always be chosen based on the type of website and the current traffic situation.
Analytics
Under the Analytics menu item, the Edge Analytics view is available. This interface displays global traffic data from the past 24 hours in chart form.
This view can help you check whether traffic is reaching the domain and how the number of requests has changed over time. The displayed data is for informational purposes and is primarily intended for a quick overview.
Frequently Asked Questions
Why is a DNS change not visible immediately?
The propagation of DNS changes is affected by TTL and caching. The Auto TTL is typically 300 seconds, so a change may take a few minutes to appear, and in some cases even longer.
Which records can use the Cloudflare proxy?
Only A, AAAA, and CNAME records that serve HTTP or HTTPS traffic are suitable for proxying. Proxying is not available for other record types.
Can email records also be proxied?
No. Records related to email generally cannot and should not be proxied. MX records are required for mail delivery, and records that are not intended for web traffic should be handled in DNS-only mode.
When should a full cache purge be performed?
A Full Cache Purge may be justified mainly when a website has been updated but old content is still being displayed. Since this removes all cached elements, the load on the origin server may temporarily increase after use.
مساعد WGS الذكي