On Thu, Oct 26, 2000 at 09:52:50AM -0700, jake wrote:
>
>The funny thing is, I called MSN support once to get the IP's of their name
>servers. They told me that as a security feature, it changes every time you
>connect, and for that reason, they themselves didn't know what the IP's of
>their name servers.
Oh, it's a security feature all right. If the network setup is too bogus to
be understood, it makes life very awkward for the attacker.
Of course, if the attacker is *outside* MSN, that's another story;
{cthulhu!maindesk#ttyp0:/home/maindesk} 0:509 bash$ nslookup -q=ns msn.com
Server: ns1.rio.com
Address: 206.96.130.10
Non-authoritative answer:
msn.com nameserver = DNS4.CP.MSFT.NET
msn.com nameserver = DNS5.CP.MSFT.NET
msn.com nameserver = DNS7.CP.MSFT.NET
msn.com nameserver = DNS6.CP.MSFT.NET
Authoritative answers can be found from:
DNS4.CP.MSFT.NET internet address = 207.46.138.11
DNS5.CP.MSFT.NET internet address = 207.46.138.12
DNS7.CP.MSFT.NET internet address = 207.46.138.21
DNS6.CP.MSFT.NET internet address = 207.46.138.20
{cthulhu!maindesk#ttyp0:/home/maindesk} 0:510 bash$
--
On two occasions I have been asked [by members of Parliament!], `Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able rightly to apprehend the kind of
confusion of ideas that could provoke such a question.--Charles Babbage
