Domain Name Server (DNS) & IP Address
By Claus Kucher
Hi Robbie, You commented on my contribution to 020123 MMDigest:
>[ Editor's note:
>[ The Internet is often overloaded and extremely slow
>[ during "rush hours" ...
>[ Launch MS-DOS prompt ...
>[ type C:\>tracert 207.212.80.187 ...
>[ But why does your web browser report "Cannot connect to ..."?
>[ Now type C:\>ping mmd.foxtail.com If replies are not
>[ returned then you can suspect that your ISP's DNS (Domain
>[ Name Server) has failed, so contact your ISP and complain!
Okay, another way is to use other name servers within good reach;
normally you can state two DNS's in a Windows system. Just try those
listed at the end of a 'whois' query (and verify they will have a
good performance).
Of course you can run your own DNS services on your machine, but
normally a simple statement of oft-used IP-number/names-translations
in your 'hosts' file will abbreviate the way and boost connecting.
Try this one (use any plain editor):
207.212.80.187 mmd.foxtail.com # I love Fuchsschwanz :-)
Additional surplus: dealing with IP-numbers instead of names is a big
complication for a 'man in the middle'-attack and/or spoofing.
Servus!
Claus Kucher
[ MMDers using Juno.com service could not connect to
[ mmd.foxtail.com because the Juno DNS had failed. Typing the
[ IP address for MMD (http://207.212.80.187/) is a simple
[ alternative to the work of finding an alternate DNS.
[ -- Robbie ("mmd.fuchsschwanz.com" ;-)
|
(Message sent Thu 24 Jan 2002, 10:42:04 GMT, from time zone GMT+0100.) |
|
|