That (almost certainly) has nothing to do with DNS.  It's looks like it's
on their server side rather than the public DNS side.  The "line of crap"
looks to me like an GUID for an error that can be used to troubleshoot
problems.


On Wed, Jun 25, 2014 at 11:17 AM, David McSpadden <[email protected]> wrote:

>  Because www.msn.com is not resolving to a valid webpage but that line of
> crap I sent earlier.
>
>
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Richard Stovall
> *Sent:* Wednesday, June 25, 2014 11:16 AM
> *To:* [email protected]
> *Subject:* Re: [NTSysADM] MSN DNS issues again.
>
>
>
> Why is that a DNS issue?
>
>
>
> On Wed, Jun 25, 2014 at 11:12 AM, David McSpadden <[email protected]> wrote:
>
> Ref A: 7679cddbc28d472f98749cf297ccf8f6 Ref B:
> 0CC853B70BC0103DA9A7B82267690A44 Ref C: Wed Jun 25 08:11:40 2014 PST
>
> This e-mail and any files transmitted with it are property of Indiana
> Members Credit Union, are confidential, and are intended solely for the use
> of the individual or entity to whom this e-mail is addressed. If you are
> not one of the named recipient(s) or otherwise have reason to believe that
> you have received this message in error, please notify the sender and
> delete this message immediately from your computer. Any other use,
> retention, dissemination, forwarding, printing, or copying of this email is
> strictly prohibited.
>
>
>
> Please consider the environment before printing this email.
>
>
>
> This e-mail and any files transmitted with it are property of Indiana
> Members Credit Union, are confidential, and are intended solely for the use
> of the individual or entity to whom this e-mail is addressed. If you are
> not one of the named recipient(s) or otherwise have reason to believe that
> you have received this message in error, please notify the sender and
> delete this message immediately from your computer. Any other use,
> retention, dissemination, forwarding, printing, or copying of this email is
> strictly prohibited.
>
> Please consider the environment before printing this email.
>

Reply via email to