Hi Ricardo,

I tried and got the same result.
It seems that DNS servers for www.sweet.com are not configured correctly.You
should investigate the problem with responsible administrator of the
sweet.com domain.
You should also contact admin(s) of following servers
nostromo.deardorff.com
eagle.deardorff.com
because sweet.com is using dns servers on these servers.


Here is the output of nslookup command



Non-authoritative answer:
sweet.com nameserver = nostromo.deardorff.com
sweet.com nameserver = eagle.deardorff.com
sweet.com nameserver = nofear.sweet.com

nostromo.deardorff.com internet address = 98.245.186.157
eagle.deardorff.com internet address = 64.92.206.84
sweet.com
primary name server = sweet.com
responsible mail addr = hostmaster.sweet.com
serial = 2008081101
refresh = 3600 (1 hour)
retry = 300 (5 mins)
expire = 3600000 (41 days 16 hours)
default TTL = 3600 (1 hour)


"Ricardo" <ricardolowe@newsgroup> wrote in message
news:eb17e2ec-848f-41fe-9eba-0863b7402dbe@newsgroup

>I recently discovered that www.sweet.com points to my localhost
> 127.0.0.1.
> Every Win XP client that I tested this on across my company and my
> list of friends on the internet have the same result.
>
> Does anyone know what this is? try it out yourself. Ping www.sweet.com
> and share with me your results. This smells like a consipiracy.