Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/dnsapi.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!

@��@ �8.rdata�@@.rsrc  @@��K
T88��K$��8.rdata8x.rdata$zzzdbg �.rsrc$01�!X.rsrc$02 .�{/�DG#�#$ҹ�,�sL���>�6m��Kx�8���P�h����������������	(	8	H	X	h�!%��,���-��<14�p3t�MOFDATAMOFRESOURCEMUIFOMBeDS}�TN�B/
NbńPT�I��&&@�$
0/@��l0-�1����(D" �y`O���{�X M�0��-�P����*F��4� ��P.D����4H��� fPOߣ`����MNȝ�ď��"�E�R@$=��
@�P�L��pl�ub�Tʧ�y��E£��P��nXBQ4�(	(B]R:.!��"��29@�1��3"HQ�	�LP�x��8�Vg���	�"�>:�N�q#`�R��CH�$0#��x=����ha�*;,����*D&��%����� ^Ї0�<	`��
�Iw>7� P~p/�Yx���x�����4�����Pt
0�CxN�5\��z"��c�t�p)���`,�FA���83O��"��@X�u,h��qx���1�
҇w����=��oxj�^�I�=
��(z>Oh``��x`��O�`C�|g�y>�bhG�Ń�̓�|b
}���)���B��ӊ�|��
=��a�yxo/��{�GN��������YD���O(�/�	!'�C�dzye�974�}v<4�q�{�z�C�|&:��Q�#��q|d�<8p������{T�Sx��@OG�C`;t~T�@��?t�������]�����?tI�w��<:e<�x6�������=������D{�8�X�'d���bG0\�x`*�O�><�����p >9��	xJ9��Ÿ��O�����������\��i��01Dܡ|�4��p�?��;u<���������SO]���|:����@țkwv�>�i����B<�{H�B'J�Q^�̃<���8�Sy��]�� N�������� z�s�����p���O��S�Dž����g� 1�?�N40?'�S��|φ�>2�#���;���������	p#�G(�# t&��P��ȏG�E�D�;��oI�E)3B(#����
�U��#`*�|D���s���H���Ŏ��B��G�@'$@�J��g�>G���?p�c)�:p�c)�z4�5	{:�cĝN�ϥ�4�1 �0�1V�W�G$�|Bac` gq&�%X~���G�s?������A
���
�g���<��u����?�C�����I2аA�����9<�9[`H����Xp�7�rZؓp<0��F����P�3����gp�
�X��a�>b�|uD�G��<8<�#p���=.ܑ�v�����#&
��OB�#8&%�S��	;��Þ�`0c�v����XNI�����S~���,���$_^?}�c�q��Ë��ǯr>6;�����!��h�B�|%��$p"�$�ѰC�04zl�

��E��<�PO�1��C���`��O��n@
;9��_w���,�_��O�
;�ˇ������ ã���<���
;B��<:@���H����O�>���<����L�+�(h�c�i�'Vܙ��zR��qc�����0p̀_^|��ٝ��O�:��X�[��=���w�	z����,�;����nO���;�Ou�p��<��1�?���	
����B8{|b'4`�?����L��
�?������t0�`���A;��oN><=�a�h��U��10����x:ȱYz��gD*a���O4�;v�s�R�=;�Ή����
vP����P���?(�<?�c���"�����{�ǟ�u��Ҁ�ɓҀ� �qH���i����4����C���;�V���4�&�a`��P�#�`�!��N�;4a�����d��3<���r����1.ܙ8���pNp�3��q���`�/�F�P\��}���y{������x�>t��#"��~�z�:���`�f``<]�%�	w.�|��6&0�=�?S&��wVۉ	0�?��#n\Ё��>�w<�ل��|R�Ք��`�`��Yx�94ё�N���p���������N��X|.��yIž�'����=tt����x#����pGSp��s��|�X��awt�%
{z������;Ƃ�̃WhӧF�V
��(ӠV�J��00[�
B#ha�� qde�< ,6���(�Ql�0�:@Xt���4��P�V@�- ,$����z�aAh3�j@X��IJ쀰� 4���Q?�� 4�k��!��	���4d�jT�0(��ci�� D8���Bb�P���8�K��<k�� rp *�?" �exb�A�@T�8 D@�De�%�  :Lw@L(��E�h��
�7L
" G�b�
���A��(� rt *�y! ����+� rD�@L�"	�x�e�A4$��BD�؁�h` *���D��Q�o$9��,�C���Qi*�X98����z�
��Ah�WH"�rD@����ɟ����Jy��hA@4TD���,�i��ѡ�Q	�;țF�Bha!Ah��́3
����2>��9����a�6AHh����=4P9��98" ��PAD�����E�A���C����Q�$����9i���V����MOFDATAMUIen-US
Parameters
DNS Client�The DNS Client service (dnscache) caches Domain Name System (DNS) names and registers the full computer name for this computer. If the service is stopped, DNS names will continue to be resolved. However, the results of DNS name queries will not be cached and the computer's name will not be registered. If the service is disabled, any services that explicitly depend on it will fail to start.%Domain Name System (DNS) Server TrustPA������� �����pAf00��0�0(�PP|���������������������L���������(������d��g��<��������������l��(The primary DNS suffix for this machine is missing. In the absence of a primary DNS suffix, short unqualified names may not resolve through DNS

The primary DNS suffix for this machine (%1) does not match the Active Directory domain (%2) that it is currently joined to.

�There was an error while attempting to read the local hosts file.

�Name resolution for the name %1 timed out after none of the configured DNS servers responded.

�Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule %1 failed with error %2

HUnable to start DNS Client service. Could not start the Remote Procedure Call (RPC) interface for this service. To correct the problem, you may restart the RPC and DNS Client services. To do so, use the following commands at a command prompt: (1) type 'net start rpc' to start the RPC service, and (2) type 'net start dnscache' to start the DNS Client service. See event details for specific error code information.

�Unable to start DNS Client service because the system failed to allocate memory and may be out of available memory. Try closing any applications not in use or reboot the computer. See event details for specific error code information.

 The system failed to register network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS Server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe cause of this DNS registration failure was because the DNS update request timed out after being sent to the specified DNS Server. This is probably because the authoritative DNS server for the name being updated is not running.%n%nYou can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still  persist, contact your network systems administrator to verify network conditions.

�The system failed to register network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.%n%n(The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.

�The system failed to register network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason it could not register was because either: (a) the DNS server does not support the DNS dynamic update protocol, or (b) the primary zone authoritative for the registering names does not currently accept dynamic updates.%n%nTo add or register a DNS host (A or AAAA) resource record using the specific DNS name for this adapter, contact your DNS server or network systems administrator.

�The system failed to register network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason it could not register was because the DNS server refused the dynamic update request. This could happen for the following reasons: (a) current DNS update policies do not allow this computer to update the DNS domain name configured for this adapter, or (b) the authoritative DNS server for this DNS domain name does not support the DNS dynamic update protocol.%n%nTo register a DNS host (A or AAAA) resource record using the specific DNS domain name for this adapter, contact your DNS server or network systems administrator.

�The system failed to register network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe system could not register the DNS update request because of a security related problem. This could happen for the following reasons: (a) the DNS domain name that your computer is trying to register could not be updated because your computer does not have the right permissions, or (b) there might have been a problem negotiating valid credentials with the DNS server to update.%n%nYou can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

TThe system failed to register network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the DNS update request could not be completed was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

�The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe reason that the system could not register these RRs was because the update request that was sent to the specified DNS server timed out. This is probably because the authoritative DNS server for the name being registered is not running.%n%nYou can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

xThe system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe cause was DNS server failure. This may be because the reverse lookup zone is busy or missing on the DNS server that your computer needs to update. In most cases, this is a minor problem because it does not affect normal (forward) name resolution.%n%nIf reverse (address-to-name) resolution is required for your computer, you can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe reason that the system could not register these RRs was because (a) either the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone where these records are to be registered does not allow dynamic updates.%n%nTo register DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

�The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe reason that the system could not register these RRs was because the DNS server refused the update request. The cause of this could be (a) your computer is not allowed to update the adapter-specified DNS domain name, or (b) because the DNS server authoritative for the specified name does not support the DNS dynamic update protocol.%n%nTo register the DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

xThe system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nYou can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

�The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

�The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at this time.%n%nYou can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

�The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.%n%nYou can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

lThe system failed to register host (A or AAAA) resource records for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nEither the DNS server does not support the DNS dynamic update protocol or the authoritative zone for the specified DNS domain name does not accept dynamic updates.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

�The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

�The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nYou can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

�The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

The system failed to update and remove registration for the network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time.

�The system failed to update and remove registration for the network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason for this failure is because the DNS server it sent the update to failed the update request. A possible cause of this failure is that the DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.%n%n

�The system failed to update and remove registration for the network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not currently accept DNS dynamic updates.

TThe system failed to update and remove registration for the network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not perform the update request was the DNS server contacted refused update request. The cause of this is (a) this computer is not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for the zone that requires updating does not support the DNS dynamic update protocol.

 The system failed to update and remove registration for the network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the system could not perform the update request was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nSee event details for specific error code information.

�The system failed to update and remove the DNS registration for the network adapter with settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe system could not update to remove this DNS registration because of a system problem. See event details for specific error code information.

�The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe system could not remove these PTR RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone that requires update is not running.

�The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address : %6%n%nThe system could not remove these PTR RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs.

lThe system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe system could not remove these PTR RRs because either the DNS server does not support the DNS dynamic update protocol or the authoritative zone that contains these RRs does not accept dynamic updates.

�The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe system could not remove these PTR RRs because the DNS server refused the update request. The cause of this might be (a) this computer is not allowed to update the specified DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol.

HThe system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe system could not remove these PTR RRs because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information.

�The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Adapter-specific Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address :%n

            %6%n%nThe system could not remove these PTR RRs because because of a system problem. See event details for specific error code information.

@The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%n

        The system could not remove these host (A or AAAA) RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone where these RRs need to be updated is either not currently running or reachable on the network.

�The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe system could not remove these host (A or AAAA) RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs.

�The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the DNS domain name specified in these host (A or AAAA) RRs does not currently accept DNS dynamic updates.

�The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe request to remove these records failed because the DNS server refused the update request. The cause of this might be that either (a) this computer is not allowed to update the DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol.

0The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason for this failure was because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information.

�The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n

          Adapter Name : %1%n

          Host Name : %2%n

          Primary Domain Suffix : %3%n

          DNS server list :%n

            %4%n

          Sent update to server : %5%n

          IP Address(es) :%n

            %6%n%nThe reason the update request failed was because of a system problem. See event details for specific error code information.

Info

 Start State

End State

$Closed State

 Open State

$Connect State

$Listen State

,Association State

4Authentication State

,Established State

Error

Warning

 Information

PMicrosoft-Windows-DNS Client Events

hMicrosoft-Windows-DNS Client Events/Operational

System

@There are currently no IPv4 DNS servers configured for any interface on this host. Please configure DNS server settings, or renew your dynamic IP settings.

�Interface: %1 Total DNS Server Count: %2 Index: %3 Address: %6 (%4)

�The DNS server being queried for interface %1 has changed to %3

�The following DNS server(s) were successfully validated as active servers that can service this client. %2

|The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. %2

�Name resolution for the name %1 timed out after the DNS server %3 did not respond.

A name not found error was returned for the name %1. Check to ensure that the name is correct. The response was sent by the server at %3.

pThe DNS server's response to a query for name %1 indicates that no records of the type queried are available, but could indicate that other records for the same name are present.

�The response for the query %1 was a Link Local IP address %3. The response was sent by the server at %5.

@There are currently no IPv6 DNS servers configured for any interface on this host. Please configure DNS server settings, or renew your dynamic IP settings.

Read DNS Name Resolution Policy Table: Key Name %1: DNSSEC Settings: DnsSecValidationRequired %2, DnsQueryOverIPSec %3, DnsEncryption %4 Direct Access Settings: DirectAccessServerList %5, EnableRemoteIPSEC %6  RemoteEncryption %7 ProxyType %8 ProxyName %9

lMatched Effective policy for query name %1: Key Name %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8

�Name resolution for the name, %1, will not fall back to LLMNR or NetBIOS

�Transaction ID of the response for query %1 from server %3 did not match

�The DNS server IP %3 of the response for query %1 is not configured on the client

�The question (%2) in the response from server %4 does not match the original question %1

�DNS Name resolution for the name, %1, failed because the client was unable to contact DNS servers. At least one of the interfaces is not in a private network and name resolution will not fall back to LLMNR or NetBIOS

�Matched effective policy for query name %1: Key Name %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8 GenericServerList %9 IdnConfig %10

�DNS Query is initiated for the name %1 and for the type %2 with query options %3

hDNS Query operation is completed with result %1

�DNS Cache lookup is initiated for the name %1 and for the type %2 with query options %3

�DNS Cache lookup operation for the name %1 and for the type %2 is completed with result %3

�DNS FQDN Query is initiated for the name %1 and for the type %2 with query options %3

�DNS FQDN Query operation for the name %1 and for the type %2 is completed with result %3

PDNS query is called for the name %1, type %2, query options %3, Server List %4, isNetwork query %5, network index %6, interface index %7, is asynchronous query %8

TDnsQueryEx for the name %1 is pending

�DNS query is completed for the name %1, type %2, query options %3 with status %4 Results %5

hNetwork query initiated for the name %1 (is parallel query %2) on network index %3 with interface count %4 with first interface name %5, local addresses %6 and Dns Servers %7

xDNS Query sent to DNS Server %3 for name %1 and type %2

�Received response from DNS Server %3 for name %1 and type %2 with response status %4

NETBIOS query is initiated for name %1 on network index %2 with inteface count %3 with first interface name %4 and local addresses %5

�NETBIOS query is completed for name %1 with status %2 and results %3

\NETBIOS query for the name %1 is pending

XDnsQueryEx is canceled for the name %1

�Cache lookup called for name %1, type %2, options %3 and interface index %4

�Cache lookup for name %1, type %2 and option %3 returned %4 with results %5

�Query wire called for name %1, type %2, interface index %3 and network index %4

�Query response for name %1, type %2, interface index %3 and network index %4 returned %5 with results %6

PError: %1 Location: %2 Context: %3

TWarning: %1 Location: %2 Context: %3

TTransitioned to State: %1 Context: %2

TUpdated Context: %1 Update Reason: %2

�SourceAddress: %1 SourcePort: %2 DestinationAddress: %3 DestinationPort: %4 Protocol: %5 ReferenceContext: %6

�Interface Guid: %1 IfIndex: %2 Interface Luid: %3 ReferenceContext: %4

static

dynamic

t4VS_VERSION_INFO��
aJ
aJ?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationNFileDescriptionDNS Client API DLLh$FileVersion10.0.19041.1 (WinBuild.160101.0800).InternalNamednsapi�.LegalCopyright� Microsoft Corporation. All rights reserved.6OriginalFilenamednsapij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.19041.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD