No announcement yet.

Server 2003 DNS issue

  • Filter
  • Time
  • Show
Clear All
new posts

  • Server 2003 DNS issue


    Today I've just realised there is an issue with DNS. The DNS Server has two entries in it's IP settings, the first one is itself, the second one is an external one.

    When you run NSLOOKUP it only checks the primary DNS server. It ignores the secondary.

    Is this a problem with Server 2003, or is it something else?

  • #2
    No problem here. Nslookup will always use the first dns server in your NIC's dns server list unless otherwise stated.

    Has anything stopped working? Is your internet ok? Has something never worked?
    Server 2000 MCP
    Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **


    • #3
      There is another problem here. Having a secondary DNS in your TCP/IP settings that points to an external server (a DNS that knows nothing of your internal DNS names) is asking for trouble. You might get to the point that internal names cannot be found anymore.

      Instead, configure a forwarder on your DNS server for that external DNS. That way your internal DNS will query the external DNS for anything it does not know. This is probably what you want.


      • #4
        Thanks, configuring a forwarder solved the main issue, which was that it wasn't resolving some names.

        To get back to the DNS server checking, if you run NSLOOKUP blah on a Win2K server, you see it hitting both DNS servers, if the first can't resolve it, but on the 2003 server it hits one, can't resolve it, and tells you so. It doesn't seem to even try the second one.


        • #5
          I didn't know there was a difference, but w2003 certainly gets it right


          • #6
            Just a side note:
            If the DNS server can not perform reverse lookup to itself, Microsoft client will fail over to secodary DNS it has configured.

   has IP of and running DNS
            If MS client can not resolve to FQDN, it will go to secondary DNS.

            Add to the mix the domain name devolution, DNS suffix search list and the fact that MS clients like to always append the primary DNS suffix to the query, and you'll get a bit of headache when troubleshooting DNS...
            Guy Teverovsky
            "Smith & Wesson - the original point and click interface"