Announcement

Collapse
No announcement yet.

DNS server misconfiguration? (server 2008 R2)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DNS server misconfiguration? (server 2008 R2)

    I have a single 2008 R2 server that is acting as a AD server and DNS server.

    the server has 1 NIC enabled which has the ip-address 192.168.92.5. As a DNS server it is pointing to itself.

    the problem is that nslookups do not work:

    C:\Users\Administrator>nslookup server
    DNS request timed out.
    timeout was 2 seconds.
    Server: UnKnown
    Address: 192.168.92.5

    DNS request timed out.
    timeout was 2 seconds.
    DNS request timed out.
    timeout was 2 seconds.
    *** Request to UnKnown timed-out

    If I leave the DNS server fields empty in the properties of the NIC (it will then automatically point to 127.0.0.1) it does work:

    C:\Users\Administrator>nslookup server
    Server: localhost
    Address: 127.0.0.1

    Name: server.domain.local
    Address: 192.168.92.5

    when doing a simple query from the monitor tab of the dns properties it fails as well. Seems to be something wrong, but I can't seem to find where it is misconfigurated. all settings seem to be the same as an other server I checked for reference.
    Last edited by ictms-ejg; 23rd December 2011, 10:47. Reason: solved

  • #2
    Re: DNS server misconfiguration? (server 2008 R2)

    Okay so on the dns server under dns enter the loopback address 127.0.0.1

    Look in dns to see if there is a (Same As Parent) A record for 192.168.92.5 and also check there is a NS record the the FQDN of the server in your zone.
    CCNA, CCNA-Security, CCNP
    CCIE Security (In Progress)

    Comment


    • #3
      Re: DNS server misconfiguration? (server 2008 R2)

      when defining 127.0.0.1 as the DNS server will work on the server but will not be a solution for clients.

      In DNS:
      (same as parent folder) Start of Authority (SOA) [98], server.domain.local., hostmaster.domain.local. static
      (same as parent folder) Name Server (NS) server.domain.local. static
      (same as parent folder) Host (A) 192.168.92.5 ?11/?9/?2011 3:00:00 PM
      server Host (A) 192.168.92.5 static
      firewall Host (A) 192.168.92.1 static
      switch Host (A) 192.168.92.254 static
      localhost Host (A) 127.0.0.1

      Comment


      • #4
        Re: DNS server misconfiguration? (server 2008 R2)

        What I mean is set the loopback on the server dns settings and use the 192.168.x.x on the clients to see if they can resolve.
        CCNA, CCNA-Security, CCNP
        CCIE Security (In Progress)

        Comment


        • #5
          Re: DNS server misconfiguration? (server 2008 R2)

          Configuring the DNS Server's TCP/IP properties to point to its IP (192.168.92.5) or 127.0.0.1 should have the same result, and would have no impact on the clients on the network. The DNS server's TCP/IP configuration doesnt impact the way that the DNS Server service, services the queries it receives.

          Now, that you opened an NSLOOKUP prompt and just type 'server' is the real issue. To always get the expected result, you should use the FQDN, so rather than just typing 'server', you should type 'server.yourDomain.tld'. You wouldnt open a browser and type http://google without the .com at the end of the FQDN?

          the reason why it works with just 'server' with one of the configurations is most likely due to the way you have configured the DNS server's domain suffix. Is this computer part of a domain? Did you check the system properties, computer name tab to see if a domain suffix is configured, check the NIC properties see if you have modified any of the defaults or added a different domain suffix there.

          with regard to your clients on the network, of course they are not going to point to 127.0.0.1 for DNS, but its OK for the DNS server to be configured that way.
          JM @ IT Training & Consulting
          http://www.itgeared.com

          Comment


          • #6
            Re: DNS server misconfiguration? (server 2008 R2)

            guys, thanks or the input so far. I guess my problems run deeper than standard DNS issues... Reinstalled DNS on the server.

            Checking the eventlog after a REBOOT gives me the following DNS related errors in order of apearance:

            event-id 4013,
            The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol

            event-id 4015,
            The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "".

            event-id 407,
            The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.92.5.

            event-id 408,
            The DNS server could not open socket for address 192.168.92.5.

            event-id 404,
            The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 192.168.92.5.

            I am worried about the unable to bind socket errors. This seems to be the root cause
            • The NIC is configured with 192.168.92.5 and is the only one enabled on the system.
            • the primary DNS server is set to 192.168.2.5
            • DNS server is set to listen to all ip addresses on the server
            • there is no other device on the LAN with the same address

            Comment


            • #7
              Re: DNS server misconfiguration? (server 2008 R2)

              the problem is solved. It was caused by Filemaker Server v9. At startup of the server it started before the dns service and used port UDP:53. Don't ask me why, because it should not do this. But then again this version is not officialy supported by Filemaker to run on Windows 2008.

              I found it using 'netstat -ano' which shows ports and PID's, after that issued 'tasklist' to show the processes and found out it was fmserver.exe using the port.

              I solved the startup issue by creating a dependence in the registry between the filemaker service and the dns service and changed the startup option for the filemaker service to startup: automatic (delayed).

              Comment

              Working...
              X