[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Sheflug] Re: My First Post - Connecting Linux to the Internet
> I doesn't necessarily have to be the
> DNS of your ISP, anyone will do. You just need to find a DNS out there on
> the internet that can resolve names into machine addresses for you; once
> you've found one if it can't resolve a name for you it passes it on to the
> next one.
>
> In Windows if you open up a DOS Prompt (while connected to the internet)
and
> type ping www.yahoo.com you'll get something like this back:
>
> Pinging www.yahoo.akadns.net [216.32.74.51] with 32
>
> Reply from 216.32.74.51: bytes=32 time=266ms TTL=240
> Reply from 216.32.74.51: bytes=32 time=275ms TTL=240
> Reply from 216.32.74.51: bytes=32 time=255ms TTL=240
> Reply from 216.32.74.51: bytes=32 time=255ms TTL=240
>
> It's a good chance that 216.32.74.51 will act a DNS for your
configuration.
>
Chris Johnson wrote:
..This is actaully a bad thing to do in general, though it may work, it
shouldn't really be used...
Good point Chris! Though what I was really trying to point out was that a
DNS of some description needs to be given in order to resolve names and
browse the web. This isn't something that I've seen manually configured in
Windows (although I know it can be) and is an obvious step to miss for
anyone coming to Linux from a Windows background - I don't actually use an
arbitrary DNS, I use the IP address provided by my ISP, though I hadn't
actually considered the abuse angle.
Thanks again for pointing out the error of my ways.
John
---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word
"unsubscribe" in the body of the message.
GNU the choice of a complete generation.