Re: Bug in server 2003 DNS policy setting

From: David Adner (davidadner_at_YAHOO.COM)
Date: 05/18/05

  • Next message: Matthew Mucker: "Re: Surprise! Windows Updates" 
    Date:         Wed, 18 May 2005 14:55:00 -0500
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM

    IPCONFIG reads from the traditional portion of the Registry where TCP/IP
    settings are stored. The GPO setting you're referring to will store the
    info in a different location. So this isn't a "bug" but simply the function
    of how IPCONFIG works. It's always behaved this way; it's nothing specific
    to 2003 SP1 or XP SP2. It won't be changed unless a sufficient number of
    customers complain.

    Someone else mentioned the DNS Search Suffix Lists also showing this
    behavior when viewed via IPCONFIG. This is for the same reason as above.

    > Enviroment:
    > Server: Windows server 2003 Domain.SP1
    > Clients: XP Pro SP2
    >
    > Symptoms:
    > In group policy you can set up a setting under computer
    > configuration > Administrative templates > Network > DNS
    > client > DNS servers so that the computers the policy is
    > applied to will be configured with the specified dns servers.
    > When the policy is applied, you run ipconfig /all on the
    > client and you will be displayed the original ( before the
    > policy was applied ) DNS configuration however when you run
    > nslookup the DNS server used is the one defined in the
    > policy. Therefore the DNS displayed in the configuration is
    > different from the one used for name resolution. 

    --
NTBugtraq Editor's Note:
Most viruses these days use spoofed email addresses. As such, using an Anti-Virus product which automatically notifies the perceived sender of a message it believes is infected may well cause more harm than good. Someone who did not actually send you a virus may receive the notification and scramble their support staff to find an infection which never existed in the first place. Suggest such notifications be disabled by whomever is responsible for your AV, or at least that the idea is considered.
--
  • Next message: Matthew Mucker: "Re: Surprise! Windows Updates"

    Relevant Pages

    • Re: Domain Controller takes a long time to boot up
      ... IPCONFIG output: Note that the default gateway is our ISA Server ... Windows IP Configuration ... Connection-specific DNS Suffix. ... What DNS servers are configureed in the DC's IP properties? ...
      (microsoft.public.windows.server.networking)
    • Re: IE & Router problem
      ... got the same results as per your note for nslookup and ipconfig commands. ... The ping command gave me the following. ... possibility that your system is seeing your DNS servers as local. ... Windows 98 and Windows Me have a shortcut in the ...
      (microsoft.public.windows.inetexplorer.ie6.browser)
    • Re: Fast downloads, slow browsing
      ... I don't think it got all of the ipconfig /all from the ... "Chuck" wrote: ... addresses of the DNS servers for this computer, ... I purchased a Linksys wireless router. ...
      (microsoft.public.windowsxp.network_web)
    • Re: DNS not resolving ip addresses
      ... This is the Ipconfig /all from a Doamin Controller ... reporting many Netlogon and other errors because of the use of these ... To fix your issues remove BOTH of these DNS servers from TCP/IP properties ... resolved to the correct IP addresses for the internet root servers. ...
      (microsoft.public.windows.server.dns)
    • Re: Records not created for Forward zone
      ... > authorative and secondary DNS servers and the IPconfig on the server ... > lists itself. ... guessing instead of having solid information to make a diagnosis. ... I hope you are not referring to Public DNS servers, ...
      (microsoft.public.win2000.dns)