none
DNS Problems? Clients loose conection, NIC freeze? RRS feed

  • Question

  • Hello everyone! I have problem probably with NIC. Sometimes the server breaks the connection for a moment, for example in RDP or in working programs It looks like a temporary freez and communication is recovered. I checked the card logs, no entries. The problem occurs only with DNS in event viewer.
    My ipconfig /all


    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : qklinika
       Primary Dns Suffix  . . . . . . . : NAME.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : N.local
                                           Business
    
    Ethernet adapter vEthernet (Intel(R) I210 Gigabit Network Connection - Virtual Switch):
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 90-1B-0E-44-11-B8
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 8.8.8.8
                                           8.8.4.4
       NetBIOS over Tcpip. . . . . . . . : Disabled
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . : Business
       Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
       Physical Address. . . . . . . . . : 90-1B-0E-47-02-AC
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.0.0.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 31 maja 2019 17:27:14
       Lease Expires . . . . . . . . . . : 4 czerwca 2019 05:27:14
       Default Gateway . . . . . . . . . : 10.0.0.1
       DHCP Server . . . . . . . . . . . : 10.0.0.1
       DNS Servers . . . . . . . . . . . : 8.8.8.8
                                           194.204.159.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Local Area Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : TeamViewer VPN Adapter
       Physical Address. . . . . . . . . : 00-FF-86-6D-34-90
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    I suppose the problem is with the Ethernet vEthernet adapter (Intel (R) I210 Gigabit Network Connection - Virtual Switch). DNS should point to router on 192.168.1.1?? Error from event viewer

    Dynamic registration or deletion of one or more DNS records associated with DNS domain 'NAME.local.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).
    
    The DNS server recv() function failed. The event data contains the error.

    Also from BPA


    he DNS server 8.8.8.8 on Ethernet did not successfully resolve the name for the start of authority (SOA) record of the zone hosting the computer's primary DNS domain name.

    The "Rfc1510KdcAtSite" Domain Name System (DNS) service (SRV) resource record that advertises this domain controller as an available Kerberos server for the domain in its local site is not registered. All Kerberos servers in the domain must register this record.

    The DNS server 8.8.8.8 on Ethernet did not successfully resolve the name _ldap._tcp.gc._msdcs.NAME.local.



    Monday, June 3, 2019 8:15 PM

Answers

  • A domain controller and all members should have the static ip address of DC listed for DNS and no others such as router or public DNS. Domain DNS is used so members can find and logon to domain. Internet queries are passed to the 13 default root hint server in a top level down fashion or optionally to configured forwarders.

     

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Monday, June 3, 2019 8:19 PM

All replies

  • A domain controller and all members should have the static ip address of DC listed for DNS and no others such as router or public DNS. Domain DNS is used so members can find and logon to domain. Internet queries are passed to the 13 default root hint server in a top level down fashion or optionally to configured forwarders.

     

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Monday, June 3, 2019 8:19 PM
  • Ok, so I should put ip of server into dns?

    Tuesday, June 4, 2019 6:27 AM
  • Correct, a domain controller and all members should have the static ip address of DC listed for DNS and no others such as router or public DNS.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, June 4, 2019 12:11 PM