Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security NTBugtraq
[Top] [All Lists]

Bug in server 2003 DNS policy setting

Subject: Bug in server 2003 DNS policy setting
Date: Mon, 2 May 2005 18:25:53 +0200
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.
--

<Prev in Thread] Current Thread [Next in Thread>