Instructions

If you want to find out DNS- server your provider, launch the command line using the “Run” utility in the “Start” menu of the Windows XP operating system or in the search Windows line Vista or Seven. Enter cmd into it and press the Enter key, after which a small black window should appear on your screen.

I'm using the Latin keyboard layout, enter ipconfig/all. You should see the most full information about the provider used, including its DNS server. Please note that at the time of execution of this action it is necessary that the connection via local network and Internet connection must be turned on.

To find out your provider's DNS, go to its official website or use another reliable source of information, then review the data regarding this information in the help section. Also, such information is often provided on payments and in information booklets provided to the company's clients.

Call the service technical support Internet provider you use, then go to the receiving section reference information, if such is provided by the auto-response system; if it is not available, contact a technical support employee to obtain the information you are interested in.

Double-left-click on your active-internet connection icon in the panel quick access in the lower right corner of the screen. A small window should open containing information about the connection. Go to the tab called “Information” and view the data of the DNS used server A. You can also find DNS data on various reference sites.

Video on the topic

Helpful advice

Learn to use the command line.

Sources:

• how do I know if I have xp or not?

Find server V networks can be done in two ways: using the ipconfig utility built into the system, which displays the main parameters networks, as well as manually. Choose the most suitable method for you.

Instructions

Run the built-in ipconfig utility. To do this, open the main menu of your operating system and select “Run”. In the “Open” field, enter the value cmd and confirm with the “OK” button to launch the “Command Prompt” tool. Enter the value ipconfig /all at the command prompt and press the command Enter keys.

Use the following command syntax to define the required parameters: - /all - display all TCP/IP configuration parameters; - /release - disable the TCP/IP protocol; - /renew - update configuration values; - /dispalydns - display the DNS cache; - / flushdns - delete the DNS cache;- /showclassid - display the DHCP class;- /setclassid - set the DHCP class.- /registerdns - register DNS names and IP addresses in manual mode.

Go back to the Start menu and try to run the definition server and in manual mode, if To do this, open the “All Programs” folder. Select "Accessories" and launch "File Explorer". Find the file called l2ini (or l2a.ini and l2ex.ini), which is located in the system folder and open it with Notepad.

Write a line that contains the IP address server and with the value ServerAddr= or use free application l2encdec.exe, available for download on the Internet and allowing you to perform the decryption operation the desired file. Enter the value -s l2.ini in the “Object” line and confirm the selected changes by clicking OK. Open the edited shortcut and in the ServerAddr= line, determine the address of the required server A.

Try searching in networks game server, if you have a similar need. For example, to search server In Counter-Strike 1.6, use the special game one by downloading and running the MasterServers.vdf file. A similar operation can be done with other network .

Video on the topic

Quite often, Internet users have difficulties accessing the network due to the fact that the Internet provider's DNS server is temporarily out of order. That is, the Internet channel is physically stable, but there is no access to resources due to the server being inoperable. In such situations, a locally configured DNS server can help. The only problem is that most Microsoft user operating systems (Windows 2000/XP/Vista) do not have a built-in DNS server, so you will have to use third-party developments.

You will need

• - a computer connected to the Internet;
• - unbound DNS server distribution.

Instructions

Before setting up your own DNS server a, consult with the provider’s support service to see if this process will interfere stable work Internet connection, whether this conflicts with the general settings for a specific provider.

Download unbound-DNS from http://unbound.net/. The installer for this DNS is server and will be located in the “Downloads” section. You must select an installer that is designed for 32-bit Windows operating systems (even if you have a sixty-four-bit operating system from Microsoft installed, most likely this application will run in compatibility mode).

Run the unbound installer (unbound _setup_X.X.X., where X is the digital designation of the version you downloaded, on the developer’s website, as a rule, you can find the latest one on this moment version), in dialog mode, follow the installer’s recommendations (where necessary, click “Next”; where prompted, read the license agreement and make a note that you have read it). At the end of the installation, you just need to confirm its completion by clicking the “Finish” button. This completes the DNS installation. server a completed. You don't need to turn it on - it starts automatically after the installation process is completed. After a reboot, it will also start automatically unless you forcefully disable it.

Configure your network connection by specifying your local host as an additional DNS (the default Localhost IP address is 127.0.0.1) - this option is suitable if two DNS were specified in the network connection settings - primary and secondary. If in the settings the option “Obtain DNS address” was checked server and automatically”, then force change the settings to manual input DNS addresses server and specify the localhost address (127.0.0.1) for both primary and secondary DNS server A.

Check the availability of Internet sites - try visiting one of them. If the Internet is working, you can forget about this problem. If not, check the availability of your ISP gateway, it may be a problem physical connection with your provider.

note

The DNS server service may be blocked by your firewall, so to be safe DNS work, you need to either disable the firewall or properly configure it to collaboration.

Helpful advice

You can find out the gateway of your Internet provider by running the command ipconfig /all in the command line

Sources:

• Running a DNS server under Windows

DNS is a domain name system that allows you to create your own for each computer on the network. Domain name. Create DNS server possible with the help of specialized software at any Windows system. If you have Windows Server 2008, then installation can be done through the control panel.

Instructions

Download the BIND program from the official website of the developer. After the download is complete, unpack the resulting archive and run the BINDInstall.exe file. For convenience, specify the path C:BIND as the Target Directory parameter, enter the user name in the Service Account Name field, and the password in the Service Account Password. These items are filled in for security purposes. Click the Install button and wait for the installation to complete.

Create configuration file named.conf in the C:BINDetc directory and enter the settings server A. Also you can find ready file in the Internet.

After completing all the settings, restart your computer and launch the command line (Start - All Programs - Accessories - Command Prompt). Enter the query:nslookupIf DNS server works, then the setup can be considered complete.

On computers with installed Windows Server you can create DNS through the control panel. Select "Start" - "Control Panel" - "Administrative Tools" - "Management" server om."

On the left side of the window, expand the “Management” tab server om" (Server Manager) and select the "Roles" object. On the right side of the panel, click “Add Roles”.

In the Role Wizard that appears, select “DNS Server”. Next, follow the wizard's instructions. Click “Install” and wait for the successful installation notification to appear.

To enter parameters server and go to the management console (Start - All Programs - Administrative Tools - DNS). To open the setup wizard, select the name of your computer and click the menu item “Actions” - “Configuration”. Following the onscreen instructions, enter required settings. When the procedure is complete, press the “Done” button.

Helpful advice

You can always check the health of the server using the nslookup utility, which is launched directly from the console window DNS management when you right-click on the created computer name.

Sources:

• BIND

In order to find out the DNS IP address - servers, just log in as an administrator and execute a series of simple steps. Even a novice in the field can cope with this operation. computer technology and working with network connections.

Instructions

Turn on your computer and go to operating system as an administrator. Bring up the main menu by clicking the Start button at the bottom left of the screen. Open the “Run” section and specify “ping” adding the domain name of your DNS servers, which should advise the data that is listed in the ADSL, or on the DNS provider’s website. Click the "Ok" button and review the result. As a result, a command line will appear, which will indicate the IP address of your servers.

Determine the IP address of the game DNS- servers. To do this, you need to launch the game and establish a connection. After that, minimize her window without quitting. Go to the Start menu and select the Run section. Type cmd in the “Open” field and press “Ok” or Enter.

Often when self-connection router, users unexpectedly discover the “DNS server” tab in the router settings and rush to the vastness of the World Wide Web in search of how to register DNS on the router.

However, before “getting into the weeds” and changing the DNS settings on the router yourself, you need to figure out what kind of “beast” this is - DNS, and why you need a DNS server at all.

We discussed this issue in more detail in the article, but here we will focus only on its main “characteristics”.

So, DNS (or domain name system) is one of the protocols that provides application layer computer networks.

It was designed to replace overly long and unmanageable (IP) domain name labels for corresponding addresses.

Thus, the main task of the DNS server is to “distribute” domain names and assign these labels connected on the section of the network entrusted to it.

Of course, there are quite a lot of main DNS servers “working” on the Internet - for different regions and continents. At the same time, all other servers request domain decryption from them (translation of domain names into IP addresses).

What is delegation?

When you have access to the Internet, the responsibility of deciphering domain names for subscribers of a given network falls on , which unites all the functional nodes of your local network.

By default, routers request the “name” of the desired network IP from the ISP’s DNS server. Wherein this operation is called delegation and occurs automatically without the “intervention” of the administrator of a given network.

However, the "default" settings have one significant drawback - this request can be delegated multiple times to multiple proxies. Thus, if problems arise with one of the servers, then instead of your favorite site, an unpleasant message will be displayed in the browser. And until the server administrators fix the problem, you will only be able to get to the desired site by IP address - i.e. knowing the decryption of his domain.

In addition, even with full functionality of each link of this network, each delegation operation takes up extra time to transmit the request and response (from your computer to one of the main DNS servers and back).

Accordingly, it makes sense to register DNS on the router manually - i.e. configure delegation directly, bypassing all intermediary servers.

Which DNS servers should I register in the router?

In principle, there are several reliable addresses that you can remember or write down, and “if something happens” you can safely use.

One of these “addresses” that can be entered into the DNS settings on the router is 8.8.8.8

This address should solve the issue of stability of access to the DNS server, but it will not be possible to “squeeze” the maximum page loading speed with its help.

To do this, you should find out which DNS server is closest to your part of the worldwide network and register it on the router.

At the same time, you can find out the “optimal” DNS server for your router using a special program from Google called Namebench.

Download this software to your network computer, open the file, click the extract button and in the window that appears, click the start benchmark button.

This operation may take several minutes.

Based on the results of these tests, the program will load a page in the browser, where the recommended servers will be listed at the top right: primary, secondary and one additional one - these are the ones that need to be entered into the DNS settings on the router.

Depending on the router model, the path to the DNS settings may vary, but this operation is always carried out and you should look for the required tab either in “General Settings” or in “Internet Connection Settings”.

“How to find out the provider’s DNS server,” - this question can sometimes arise both from experienced users and from people solving their problem with network access. It may arise when it is necessary to configure access to the Internet through an internal network, using a specific DNS server address, and not an automatically determined address. Typically, this may be necessary if some difficulties constantly arise with the dynamic address pool. This connection is more stable and allows you to set up DSL access without interruptions in the line.

The most simple option The way to find out your DNS provider is to call support. Operators usually provide two addresses that you can enter into your network settings. If for some reason this cannot be done, use our tips below.

Administrator's advice! If there is a problem with network access. Perhaps the DNS address determination service is not working correctly, as a result you will have physical access to the network, but without access to the Internet through the browser. This can be fixed by simply restarting the computer; experienced users can restart the service and restore the network via the http protocol.

How DNS works

The principle of operation of DNS (Domain Name Services) is well demonstrated in the illustration. The user sends the usual text name of the site and in response receives an IP address through which access to a specific resource is already available. DNS is global network server-routers providing serial connection to the server system and access.

Administrator's advice! Regular users do not need to configure network settings and clarify the DNS provider and other sites. But for general development, you need to know that each text name is associated with a specific IP address, for example, 78.1.231.78.

DNS spoofing is a classic hacker attack

Experienced users will be interested in familiarizing themselves with the diagram of servers that provide access to the Internet. There is also a DNS server that routes user traffic on the side of your provider.

Administrator's advice! Please note that if you spoof the DNS server, you may be able to connect to a “fake” site. Using this interface, passwords and data are stolen credit cards. This issue is usually resolved by installing anti-virus software that includes protection against such “traffic eavesdropping.”

DNS provider

As we said, to configure network connection The provider's DNS address is required. Usually there are several of them, especially for large telecommunication systems to which many users connect. Usually, you can find out the primary and secondary DNS in the support service; these servers duplicate each other when things are going wrong huge pressure when users connect.

Determining the DNS provider from your network

The easiest way to do this is when there is a network and Internet access, or the same can be done from a subscriber who is also served in your provider network. For these purposes, follow the instructions:

• Launch Command Prompt by clicking the Start menu, then Run, and typing in CMD line(lowercase);
• in the command line window that opens, type ipconfig/all;
• in the report you will receive a list of DNS addresses;
• the received addresses can be physically registered in the network settings; in this case, access to the network will work stably even if the automatic detection of DNS servers fails.

This method helps make network access more stable; in fact, you assign a permanent DNS server with a backup address. Both servers will route your requests on the Internet.

Screenshots

Examples are shown in the screenshots. In the first case, standard server addresses are indicated. In the second case, reserve and additional. In this option, users have access to three backup servers.

Report after running the ipconfig /all command with one DNS mirror

Report after running the ipconfig /all command with two DNS mirrors

Alternative ways to find provider DNS addresses

If you do not have access to the network, the support service does not provide direct DNS addresses and you cannot get them in any other way, try searching through an Internet search. This can be done using search engine And keywords“DNS addresses (name of your provider).” In some cases, this information may be posted on the official website of the telecommunications company or in forums by users.

Views: 123327

0

Configuring a DNS server to point to itself

One of the first tasks that should be performed immediately after installing a DNS server is to configure its TCP/IP settings so that it points to itself when DNS name resolution occurs, unless there is a special reason that it didn't do this.

3. In the window Network connections click right click mouse on the Local Area Connection icon and select context menu Properties item.

4. Double-click Internet Protocol (TCP/IP).

5. In the section of the window that is associated with the DNS server, make sure that the Use the following DNS server address radio button is selected, and enter the IP address of your DNS server in the “Preferred DNS server” field.

6. If there is another DNS server, specify its IP address in the Alternate DNS server field.

7. Click OK twice to changes made came into force.

Setting up a DNS server

1. Open the Server Manager console.

2. Expand the Roles, DNS Server and DNS nodes in sequence, then click on the DNS server name.

3. From the Action menu, select Configure DNS Server.

4. On the Welcome page of the DNS Server Configuration Wizard, click Next.

5. Select the Create forward and reverse lookup zones radio button (recommended for large networks) and click the Next button.

6. Select the option Yes, create a zone live view now (recommended) and click Next.

7. Specify what type of zone you want to create, in in this case selecting the Main Zone option and clicking the Next button. If the server is a domain controller with write access, the Save zone in check box will also be available for selection. Active Directory.

8. If you save the zone in Active Directory, select the replication scope and click the Next button.

9. Enter the zone's fully qualified domain name (FQDN) in the Zone Name field and click Next.

10. At this stage, if you create a zone that is not integrated with AD, you can either create a new text file for a zone, or import an existing one. In this case, select the Create option new file with this name and leave the default settings, then click on the Next button to continue.

11. On the next page you will be asked to allow or block the DNS server from receiving dynamic updates. In this example, we will prohibit the DNS server from accepting dynamic updates by selecting the Prohibit dynamic updates radio button and clicking the Next button.

12. The next page asks you to create a reverse lookup zone. In this case, select the Yes, create reverse lookup zone now radio button and click Next.

13. Specify that the reverse lookup zone should be the main zone by selecting the Main zone radio button and click the Next button.

14. If you save this zone in Active Directory, select the replication scope and click Next.

15. Leave the default IPv4 Reverse Lookup Zone option selected and click Next.

16. Enter the network ID for the reverse lookup zone and click Next. (Typically, the Network Identifier is the first set of octets from the zone's IP address. For example, if the network uses the Class C IP address range 192.168.0.0/24, then the Network Identifier can be entered as 192.168.0.

17. If you create a zone that is not AD-integrated, you will again be prompted to either create a new file for the zone or import an existing one. In the example under consideration, select the Create a new file with the same name radio button and click the Next button.

18. You will then be prompted to indicate whether dynamic updates should be allowed. For the purposes of this example, select the Prohibit dynamic updates radio button and click Next.

19. On the next page you will be asked to configure the repeater settings. In this example, select the No, you should not forward requests radio button and click Next.

20. The final screen will provide a summary of those selected for inclusion and addition to the database DNS changes and zones. Click the Finish button to make all these changes and create the desired zones.

Open the Server Manager console. Expand sequentially the nodes Roles, DNS server, DNS, server name, forward lookup zones and select the zone we created.

Open server manager. To open Server Manager, click Start, then select Server Manager.

In the results pane, under Role Summary, click Add Roles.


In the Add Roles Wizard, when the Before You Begin page appears, click Next.
In the Roles list, click DNS Server, and then click Next.


Read the information on the DNS Server page, and then click Next.
On the Confirm Installation Settings page, verify that the DNS Server role will be installed, and then click Install.

Settings

To configure DNS server settings, right-click the name the desired server and select Properties from the context menu.

On the Interfaces tab, you can specify the IP addresses of the interfaces that the DNS server will “listen” to and respond to DNS queries. Changing this parameter only makes sense when using several network adapters or when configuring multiple IP addresses for network interfaces.

If the Listen switch is set to All IP addresses, the DNS server responds to requests received through any network interface. If the switch is set to Only at specified IP addresses, add to the list the IP addresses through which the server will serve requests - enter them in the IP address field and click the Add button. Clicking the Delete button removes the address from the list.

On the Forwarding tab, you can configure the IP addresses of the servers used to forward DNS queries. Your DNS server will forward all requests that are not within its area of ​​responsibility to the specified servers. In this case, in relation to upstream servers, it behaves like a DNS client. The request forwarding method is convenient to use firewalls(firewall) for protection internal network: Internal DNS servers forward all name resolution requests to external ones. This method can also be used to reduce traffic on channels with low throughput- in this case, all requests are redirected to the provider's DNS server, which, in turn, performs name resolution.

Using the IP address field and the Add and Remove buttons, you can specify a list of servers to which requests will be forwarded. The Up and Down buttons are used to change the order of DNS server queries. If the first server does not respond within the time specified in the Forward Timeout field, the request will be sent to the next server in the list, and so on. If none of the listed servers was able to respond to the DNS query within the allotted time, Custom DNS - the server tries to perform a recursive request to resolve the name on its own. Selecting the Don't use recursion check box prevents the server from executing recursive queries, and it returns an error message.

On the Advanced tab you can configure Extra options DNS servers. They are loaded at startup DNS services-server from an information boot file, system registry or Active Directory. In most cases, the default parameter values ​​do not require modification.

In the Server version number field, you can find out the version number of the DNS server service. This may be necessary to determine the compatibility of the Windows DNS server service with other DNS servers.

The Name check drop-down list allows you to select a method for checking names when changing records using the Management Console. The following values ​​are possible:

Strict adherence to RFC (ANSI) - all entered names must fully comply with the requirements of the RFC 1123 standard;

• Non (Non) RFC (ANSI) - it is allowed to enter non-standard names that are not allowed by the RFC 1123 standard;
• Multibyte (UTF8) - allows entering names containing non-ASCII characters, including characters in Unicode encoding, which usually require more than one byte to be stored. This scan mode is selected by default.

The Load zone at startup drop-down list allows you to specify where the DNS server service parameters will be loaded from when it starts. The following values ​​are possible:

From the registry - DNS server service parameters are loaded from the system registry. To store service parameters, the registry branch HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS\Parameters is used. From file - service parameters are loaded from special file by analogy with BIND servers(Berkeley Internet Name Domain). To use this mode, you need a boot file (usually named Named.boot) from another DNS server that uses BIND. On Windows Server 2003, this file should be named boot and located in the %systemroot%\system32\dns folder. The file must be in the earlier BIND 4 format rather than BIND 8. For all settings not configured through the boot file, the values ​​from the system registry will be used. From Active Directory and the registry - DNS server service settings are loaded from Active Directory and the system registry. This boot mode is the default.

By selecting the Allow automatic deletion of stale records check box, you enable the automatic deletion of stale DNS server zone records. To mechanism automatic update worked, it should be enabled for the server as a whole. In the Purge period field, enter the period of time after which obsolete records are analyzed and removed. For server performance reasons, it is not recommended to set the period automatic deletion less than 1 hour.

Clicking the Restore Defaults button will restore the settings to their default values.

When storing the configuration in boot file or in system registry To apply the new parameter values, you must restart the DNS server service. When storing configuration in Active Directory, some settings take effect when you click OK in the Properties window.

On the Root Links tab, you can edit the list of root DNS servers responsible for serving the root zone called "." (dot). This information is used by the DNS server when making recursive name resolution queries.

Information about root servers is stored in the file %systemroot%\system32\DNS\ Cache.dns. You can edit it manually in a text editor, or use the Root Links tab of the DNS server properties window. The Cache.dns root reference file is automatically created and populated the first time you start the Windows Server 2003 DNS Server service.

You can update or modify the root ref file depending on the DNS server configuration you are using.

If your network is connected to the Internet, you can update the cache.dns file if necessary by downloading new version root link file Named.root at ftp://rs.internic.net/domain/named.root. Rename the resulting file to cache.dns. If your network is not connected to the Internet, you can save the cache.dns file in a safe place, clear it, and add the addresses of the servers responsible for serving the root domain. On servers serving the root domain, this file can be completely deleted, since it is not needed for normal operation of root servers.

To add a new root server, click the Add button. In the window that appears, enter the DNS name of the server (or, if it is defined in one of the zones served by local server, find it by clicking the Browse button). If the corresponding host already has a DNS domain name, click the Match button to obtain the host's IP address. If it does not yet have a DNS domain name, specify one or more server IP addresses yourself by sequentially entering them in the IP address field and clicking the Add button. To add a DNS server, both its name and at least one IP address must be specified. After filling in all the required fields, click OK.

To change the root server information, click the Edit button.

When adding root server Two entries are written to the cache.dns file: the NS entry of the server and the A entry of the corresponding host. The A record is added whether it is defined in any zone or not. This record is called a glue record and is intended to ensure that the corresponding host name can be used even if the zone in which it is defined is inoperable. The Windows Server 2003 DNS server adds glue records for all servers specified in the NS records.

Below is the content standard file cache.dns:

Cache.dns -- DNS CACHE FILE Initial cache data for root domain servers. YOU SHOULD CHANGE -> Nothing if connected to the Internet. Edit this file only when updated root name server list is released. OR -> If NOT connected to the Internet, remove these records and replace with NS and A records for the DNS server authoritative for the root domain at your site. Note, if you are a root domain server, for your own private intranet, no cache is required, and you may edit your boot file to remove it. This file holds the information on root name servers needed to initialize cache of Internet domain name servers (e.g. reference this file in the "cache . " configuration file of BIND domain name servers). This file is made available by InterNIC under anonymous FTP as file /domain/named.root on server FTP.INTERNIC.NET last update Nov 5, 2002 related version of root zone 2002110501 formerly NS.INTERNIC.NET

3600000 IN NS A.ROOT-SERVERS.NET. A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4

Formerly NS1.ISI.EDU

3600000 NS B.ROOT-SERVERS.NET. B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107

Formerly C.PSI.NET

3600000 NS C.ROOT-SERVERS.NET. C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12

Formerly TERP.UMD.EDU

3600000 NS D.ROOT-SERVERS.NET. D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90

Formerly NS.NASA.GOV

3600000 NS E.ROOT-SERVERS.NET. E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10

Formerly NS.ISC.ORG

3600000 NS F.ROOT-SERVERS.NET. F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241

Formerly NS.NIC.DDN.MIL

3600000 NS G.ROOT-SERVERS.NET. G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4

Formerly AOS.ARL.ARMY.MIL

3600000 NS H.ROOT-SERVERS.NET. H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53

Formerly NIC.NORDU.NET

3600000 NS I.ROOT-SERVERS.NET. I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17

Operated by VeriSign, Inc.

3600000 NS J.ROOT-SERVERS.NET. J.ROOT-SERVERS.NET. 3600000 A 192.58.128.30

Housed in LINX, operated by RIPE NCC

3600000 NS K.ROOT-SERVERS.NET. K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129

Operated by IANA

3600000 NS L.ROOT-SERVERS.NET. L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12

Housed in Japan, operated by WIDE

3600000 NS M.ROOT-SERVERS.NET. M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33

End of File

Do not change the list of root servers unless absolutely necessary! Using incorrect addresses in this list or clearing it may result in recursive DNS queries failing, which in turn will result in virtually all domain names being unable to be resolved.

On the Debug Logging tab, you can configure the list of parameters that are logged in the DNS server log. The log is located in the file %systemroot%\system32\dns\dns.log. To start logging, enable at least one logging option and click OK.

To enable an option, select the appropriate checkbox.

The following events can be recorded in the log:

Requests and transfers - all client requests for name resolution are recorded; Notification - notifications sent to the server by other DNS servers are recorded; Update - all dynamic updates are recorded; Request - the main parameters of the name resolution request are recorded; Response - the main parameters of the response to a name resolution request are recorded; Outgoing - the number of requests sent by the DNS server is recorded; Incoming - the number of requests received by the DNS server is recorded; UDP - the number of requests received by the DNS server via the UDP port is recorded; TCP - the number of requests received by the DNS server via the TCP port is recorded;

The DNS server logging feature is intended solely for debugging its operation and should not be used to normal operation server due to its high resource intensity.

On the Monitoring tab, you can check the server's health by running a series of standard queries to this and other DNS servers.

You can use two types of tests.

A simple request to this DNS server - for the test, a local DNS client is used, with the help of which an iterative request is sent to the DNS server (with recursion prohibited); Recursive query to other DNS servers - for the test, a local DNS client is used, with the help of which a recursive query is sent to the DNS server.

Once you select at least one test, the Test button will become available. In addition, by selecting the Automatic testing checkbox and the desired check interval in the Test interval field, you can enable automatic multiple checks of the server at certain time intervals. A single or multiple test is started by clicking the Test button.

Test results are displayed in the table at the bottom of the window. It displays the date and time each test was executed, as well as the result (PASS or ERROR) of simple and recursive queries.

The Security tab allows you to set access rights to DNS service objects for specific users and user groups, thereby establishing the level of security and security of the service.