Full Disclosure mailing list archives
Re: Possible DNS compromise/poisoning?
From: DanBUK <danbuk () gmail com>
Date: Wed, 05 Jan 2005 18:29:10 +0000
I see the same, but I don't think there is an issue. C:\WINDOWS>nslookup Default Server: pmsidc03.pmsi.local Address: 192.168.42.13
set type=cname www.microsoft.com
Server: pmsidc03.pmsi.local Address: 192.168.42.13 Non-authoritative answer: www.microsoft.com canonical name = www.microsoft.com.nsatc.net
set type=a www.microsoft.com
Server: pmsidc03.pmsi.local
Address: 192.168.42.13
Non-authoritative answer:
Name: www.microsoft.com.nsatc.net
Addresses: 207.46.156.252, 207.46.244.188, 207.46.245.156, 207.46.249.252
207.46.250.252, 207.46.144.222, 207.46.156.156, 207.46.156.220
Aliases: www.microsoft.com
Cheers,
DanBUK.
DanB UK
London, UK.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Possible DNS compromise/poisoning? nicholasnam (Jan 05)
- Re: Possible DNS compromise/poisoning? KF (lists) (Jan 05)
- Re: Possible DNS compromise/poisoning? Florian Weimer (Jan 05)
- RE: Possible DNS compromise/poisoning? ALD, Aditya, Aditya Lalit Deshmukh (Jan 05)
- Re: Possible DNS compromise/poisoning? DanBUK (Jan 06)
- Re: Possible DNS compromise/poisoning? J.A. Terranson (Jan 06)
- Re: Possible DNS compromise/poisoning? Ben McGinnes (Jan 07)
- <Possible follow-ups>
- RE: Possible DNS compromise/poisoning? Madison, Marc (Jan 06)
- RE: Possible DNS compromise/poisoning? nicholasnam (Jan 06)
