IP Address vs. DNS and Finding A Site's IP Address

[Aegis]

69.147.114.210 = yahoo?
64.233.160.104 = google?

I had a customer lose internet service with Comcast.  When I used to have Comcast, they used to lose the DNS server on a more frequent basis than I think ought to happen with an ISP.

I used to test with one of the above IP addresses, but they won't work from my location.  Would a firewall block an IP address?  Why would it "care"?

Is there an easy way to get a site's IP, just for future reference?

[jamesj2001]

ping google.com

from a command prompt

[Aegis]

Yeah, I knew that.   

I'll check to see if they've changed.

Thanks for the suggestion.   

=====

I also ought have remembered that IP addresses are not written in stone -- not by far!  The reason the above addresses weren't working is because they're no longer valid!  (To think that Yahoo and Google didn't "clear" this with me!)   

[jamesj2001]

Were you asking something different?  Maybe I didn't understand.

[Aegis]

No, we're fine!

As I edited above, the addresses had simply changed!

Going to the sites via IP address works just fine when the addresses are correct!

Thanks, again, for the suggestion.  I wish they were all that easy! 

[Rob Pomeroy]

The OpenDNS service might help customers such as these.  They're not obliged to use their own ISP's DNS servers.  OpenDNS provides other benefits too, such as a measure of rouge site protection.