Re: Bug in server 2003 DNS policy setting

From: James D. Stallard (james_at_LEAFGROVE.COM)
Date: 05/17/05

  • Next message: John Gray: "Re: MS Updates SP1 for Windows Server 2003" 
    Date:         Tue, 17 May 2005 21:38:32 +0100
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM

    Tommaso, et al

    Clients also behave this way when using similar policy settings to control
    the DNS Suffix Search List. I have noticed this behaviour on a variety of
    Windows clients and servers, with Windows 2000 and 2003 Active Directory and
    Windows 2000/XP clients.

    The Windows 2000/XP clients were at SP4 and SP1 respectively, and with this
    in mind, I don't believe it is related to XPSP2 or the specific version of
    Active Directory.

    Regards

    James D. Stallard
    Microsoft and Networks Infrastructure Technical Architect
    Leafgrove Limited
    Web: www.leafgrove.com
    Email: james@leafgrove.com
    Mobile: +44 (0) 7979 49 8880

    -----Original Message-----
    From: Windows NTBugtraq Mailing List
    [mailto:NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM] On Behalf Of Tommaso Calosi -
    SYSMIC SRL
    Sent: 02 May 2005 17:26
    To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
    Subject: Bug in server 2003 DNS policy setting

    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.

    ------------------------------------------------------------------------ 

    --
                      Tommaso Calosi
                      System Engineer
                          SysMic SRL
------------------------------------------------------------------------
--
--
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.
--
--
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: John Gray: "Re: MS Updates SP1 for Windows Server 2003"

    Relevant Pages

    • Re: Questions on putting up a new DNS server.
      ... > Root domain AD-zone info. ... There are no other servers or clients in the Root domain. ... own DNS servers -- integrate them into AD. ...
      (microsoft.public.win2000.dns)
    • Major Issues After NT4 --> 2003 Upgrade
      ... For some reason, the servers are joining the DNS domain name, instead of the ... Our NT4 domain we'll call "NBIOS" and the DNS domain name that we assigned ... finding that the clients started thinking they were joined to the DNS.com ...
      (microsoft.public.windows.server.migration)
    • Re: DCs to use their own DNS/Domain name, while clients use another
      ... > -All client/member servers configured to use DNS servers that host the ... members should be in that domain for DNS as well. ... Pretty silly since the domain clients are using the BIND set. ...
      (microsoft.public.win2000.dns)
    • Re: AD circuitous route to DNS
      ... I had not even enabled forwarders to the campus DNS for Internet ... The campus DNS administrator is simply forwarding back to my AD DNS ... server from his non-AD name servers after my clients look to his servers for ... clients only since we have our own subnet. ...
      (microsoft.public.windows.server.dns)
    • Re: Change IP subnet for a site
      ... > The only problem being that the network is part of a private network in ... > clients are connected, but I have to allow for the possibility that they ... >>> servers. ... >>> DNS to ensure proper DNS registration. ...
      (microsoft.public.windows.server.active_directory)