Windows Server 2003 DNS Lookup Problems

Discussion in 'DNS Server' started by djb, Jun 2, 2005.

  1. djb

    djb Guest

    We are having problems with our W2K3 servers and DNS. We have 3 DNS servers
    that are AD-Integrated, two W2K3 and 0ne W2K. The TCP/IP configuration has
    all three DNS servers listed with the two W2K3 DNS servers listed first and
    second. This is true for all servers and WXP clients. From the clients when
    doing a NSLOOKUP, the name is resolved without any delay from the primary DNS
    server. If this DNS server is shut off, then it queries the secondary DNS
    server. If both the primary and secondary DNS servers are not available,
    then it queries the third DNS server and resolves the address. This is the
    way that I would expect this to work. On any one of the W2K3 servers, this
    is not true. If the server can not query the primary DNS server to resolve
    the address, then the query fails. The W2K3 server does not try to query the
    secondary DNS or the third DNS server. This is true with any of the W2K3
    servers, DC or member server. The W2K servers work as expected.

    All servers and clients are current with service packs and security hot
    fixes.

    Is there a way to fix this?
     
    djb, Jun 2, 2005
    #1
    1. Advertisements

  2. djb

    Todd J Heron Guest

    Can we see an ipconfig /all from a W2K3 server and a W2K server?
     
    Todd J Heron, Jun 3, 2005
    #2
    1. Advertisements

  3. djb

    djb Guest

    Windows 2000 Server:


    Windows 2000 IP Configuration



    Host Name . . . . . . . . . . . . : acitermserver
    Primary DNS Suffix . . . . . . . : aubcon.com
    Node Type . . . . . . . . . . . . : Broadcast

    IP Routing Enabled. . . . . . . . : No

    WINS Proxy Enabled. . . . . . . . : No

    DNS Suffix Search List. . . . . . : aubcon.com

    Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:



    Connection-specific DNS Suffix . : aubcon.com
    Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter
    (10/100)
    Physical Address. . . . . . . . . : 00-C0-9F-04-BB-DC

    DHCP Enabled. . . . . . . . . . . : No

    IP Address. . . . . . . . . . . . : 205.242.131.8

    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Default Gateway . . . . . . . . . : 205.242.131.248

    DNS Servers . . . . . . . . . . . : 205.242.131.10
    205.242.131.11
    205.242.131.9
    Windows Server 2003:

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : taci
    Primary Dns Suffix . . . . . . . : aubcon.com
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : aubcon.com

    Ethernet adapter TEAM #0:

    Connection-specific DNS Suffix . : aubcon.com
    Description . . . . . . . . . . . : TEAM : Team #0
    Physical Address. . . . . . . . . : 00-04-23-A6-20-76
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 205.242.131.50
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 205.242.131.248
    DHCP Server . . . . . . . . . . . : 205.242.131.9
    DNS Servers . . . . . . . . . . . : 205.242.131.10
    205.242.131.11
    205.242.131.9
    Lease Obtained. . . . . . . . . . : Thursday, June 02, 2005 11:52:49 AM
    Lease Expires . . . . . . . . . . : Thursday, June 02, 2005 4:02:49 PM

    djb
     
    djb, Jun 3, 2005
    #3
  4. For the TCP/IP properties of your servers, I would think that you should only
    list that server's IP address for DNS server, and delete the entries for the
    other servers.

    Then, in the DNS snap-in enable DNS forwarding to all name servers. Your
    other 2 servers should automatically receive forwards from the other 2
    servers since you are running an AD Integrated Zone.

    Hope this helps.
     
    Eric the IT Idiot, Jun 7, 2005
    #4
  5. djb

    djb Guest

    I am not sure that I understand your suggestion. How will changing the DNS
    server IP configuration and DNS forwarding change the results of a Windows
    Server 2003 member server’s NSLOOKUP results? The W2K3 member server works
    fine as long as the primary DNS server is available. If the primary DNS
    server is not available, the NSLOOKUP will not look for any additional DNS
    servers and the lookup will fail. This is repeatable on all of the W2K3
    servers, even the DNS server systems. I don’t remember having this problem
    before service pack 1 was installed. I’m I missing something?
    djb
     
    djb, Jun 7, 2005
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.