On 07/28/2011 12:23 PM, Viesturs Lācis wrote: > But the result I got in terminal means that my DNS finds that site, right? > I tried pinging both IP adresses and kelinginc.net domain with 100% packet > loss: > > vie@vie:~$ ping 98.139.135.22 > PING 98.139.135.22 (98.139.135.22) 56(84) bytes of data. > ^C > --- 98.139.135.22 ping statistics --- > 20 packets transmitted, 0 received, 100% packet loss, time 19151ms > > vie@vie:~$ ping 98.139.135.21 > PING 98.139.135.21 (98.139.135.21) 56(84) bytes of data. > ^C > --- 98.139.135.21 ping statistics --- > 33 packets transmitted, 0 received, 100% packet loss, time 32254ms > > vie@vie:~$ ping kelinginc.net > PING kelinginc.net (98.139.135.21) 56(84) bytes of data. > ^C > --- kelinginc.net ping statistics --- > 1529 packets transmitted, 0 received, 100% packet loss, time 1537015ms > > > Any ideas, why DNS finds the site, but I cannot open it? > I already e-mailed my ISP about that. > > Viesturs > Viesturs,
No, that just means that your local DNS server has an IP address for that domain name, most likely stored in it's cache. That doesn't necessarily mean that the machine you are on has a working route to that IP address. Mark ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
