Security Incidents mailing list archives
Re: DNS poisoning to Korean address
From: terry white <twhite () aniota com>
Date: Tue, 13 May 2003 17:34:43 -0700 (PDT)
on "5-13-2003" "Iso Mage" writ: : Interestingly, boston.com seems to have removed their DNS records from : the net. ... dig offered this from 206.124.156.n ;; boston.com, type = A, class = IN ;; ANSWER SECTION: boston.com. 59m14s IN A 66.150.192.100 ;; AUTHORITY SECTION: boston.com. 59m14s IN NS auth02.ns.harvard.net. boston.com. 59m14s IN NS auth01.ns.harvard.net. ;; ADDITIONAL SECTION: auth02.ns.harvard.net. 21h38m5s IN A 209.21.182.4 auth01.ns.harvard.net. 21h38m5s IN A 140.239.140.239 -- ... i'm a man, but i can change, if i have to , i guess ... ---------------------------------------------------------------------------- *** Wireless LAN Policies for Security & Management - NEW White Paper *** Just like wired networks, wireless LANs require network security policies that are enforced to protect WLANs from known vulnerabilities and threats. Learn to design, implement and enforce WLAN security policies to lockdown enterprise WLANs. To get your FREE white paper visit us at: http://www.securityfocus.com/AirDefense-incidents ----------------------------------------------------------------------------
Current thread:
- DNS poisoning to Korean address Iso Mage (May 13)
- Re: DNS poisoning to Korean address terry white (May 13)
- RE: DNS poisoning to Korean address Mike O'Shaughnessy (May 14)
- More Info: DNS poisoning to Korean address Iso Mage (May 14)
- <Possible follow-ups>
- re: DNS poisoning to Korean address meowbaby (May 15)
- Somewhat OT: DNS poisoning to Korean address Anders Reed Mohn (May 16)
- Re: DNS poisoning to Korean address terry white (May 13)