full-disclosure - Possible DNS compromise/poisoning?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YaUHr70J.1104949750.5026180.dan@digibox.daemonbox.de>
From: danbuk at gmail.com (DanBUK)
Subject: Possible DNS compromise/poisoning?

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.