Announcement

Collapse
No announcement yet.

DNS Problem

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

  • DNS Problem

    Hi guys,

    I got another problem

    I configured a Windows Server 2003 Enterprises Edition as a DNS server on my network.The DC is a Win2000 server,similarly the DHCP server.Client macines are WinXP SP2.I set up a primary DNS zone on it,and it's status shows me that it is running,and I also set up zone transfers to another DNS server at our headquaters.I work for the governement education department,and we have our main IT department at the ministry HQ.

    So then I tried to test my DNS by running the nslookup command from a client machine.The machines don't seem to identify the DNS server.

    This is the message I get..

    "DNS request timed out.Timeout was 2 seconds.
    ***Can't find server name for address 10.97.21.6.Timed out.
    Default server: name of DNS server at HQ
    Address: 10.0.4.129."

    10.97.21.0 is my subnet address.10.0.4.129 is the IP address of the DNS server at HQ.

    When I ping my DNS server from the machines,it replies.

    I also checked event viewer for my DNS and found out that zone transfer to the DNS server at HQ failed.It's probably their configurations that side,and it's not my concern.What concerns me is,why would my client machines ignore my DNS server here and contact another DNS server in another network?

    Any help will be highly appreciated.

    Edited to add..

    I just set up a reverse looup zone, and when I run the nslooup command the meassge changed to..


    "***Can't find server name for address 10.97.21.6: Non-existant domain.
    Default server: name of DNS server at HQ
    Address: 10.0.4.129."

    ???
    Last edited by Giodino; 29th February 2008, 14:53.

  • #2
    Re: DNS Problem

    Your client has to recieve the ip of a dns server in order to contact it.
    This is eather done by DHCP or manual.

    If by DHCP, change the DNS option to the correct server.
    [Powershell]
    Start-DayDream
    Set-Location Malibu Beach
    Get-Drink
    Lay-Back
    Start-Sleep
    ....
    Wake-Up!
    Resume-Service
    Write-Warning
    [/Powershell]

    BLOG: Therealshrimp.blogspot.com

    Comment


    • #3
      Re: DNS Problem

      Originally posted by Killerbe View Post
      Your client has to recieve the ip of a dns server in order to contact it.
      This is eather done by DHCP or manual.

      If by DHCP, change the DNS option to the correct server.
      Thanks for the reply.

      I manually configured my client with the IP address of the DNS server,and I also configured my DHCP server to allocate the address to clients dynamically.

      Comment


      • #4
        Re: DNS Problem

        Ok guys,I managed to solve the problem.

        Didn't do much though,all I had to do was restart the DHCP server,DNS server and the domain controller and WHAM!!We're up!DNS server is working!

        It solved another problem I had of applying group policies.I set up a policy to hide system drives (C: drives) on client machines,but it just couldn't get applied.With the help of guys on this forum,I realised it was a DNS problem.I had no DNS server.How this network ran without it I just don't no!!??

        Now the policy is getting applied.

        Thought I could share!!

        Cheers guys!!

        Comment

        Working...
        X