The command line, DNS cache clear, nslookup, traceroute, and ping. OH MY. [final draft]

Mar 12, 2010 22:13

Okay, I think this should incorporate everything from http://community.livejournal.com/howto_userdoc/162458.html to make this a final draft.

This should be filed under the existing Memory Category @ General Tutorials


Create 'Opening the Command Prompt or Terminal'

DISCLAIMER: This document is not an official LiveJournal document. It is a resource document maintained by a fellow user. The original source of information is noted, where available. LiveJournal takes no responsibility for the information found in this document.

Open a Command Prompt or Terminal

Windows 2000/XP:

Click Start, then select Programs, Accessories, and then Command Prompt.

Windows Vista:
Click the Vista logo, then select All Programs, Accessories.
Right-click Command Prompt and select Run As Administrator.

Macintosh OS X:
Click Applications, then open Utilities, then open Terminal.

Linux:
Due to the number of Linux flavours, if you are not sure how to access the command prompt or terminal, please consult your system's documentation or technical support resources.

Copying text from a Command Prompt or Terminal

Windows XP/Vista

1. Right-click and select 'Mark' from the right-click menu.

2. Select the text you would like to copy.

3. Press the Enter or Return key to copy the selected text.

4. Paste the text as appropriate, by holding down the 'Control' key and pressing the 'V' key.

Macintosh OS X

1. Select the text you would like to copy.

2. Copy the text by holding down the 'Command' key (also called the Apple key) and pressing the 'C' key.

3. Paste the text by holding down the 'Command' key and pressing the 'V' key.

Linux:
Due to the number of Linux flavours, if you are not sure how to copy text from the command prompt or terminal, please consult your system's documentation or technical support resources.

These should be filed under a new category "@ Troubleshooting Tutorials":


Edit ' Clearing DNS Cache: Windows, Macintosh OS X and OS X 10.5, and Linux'

DISCLAIMER: This document is not an official LiveJournal document. It is a resource document maintained by a fellow user. The original source of information is noted, where available. LiveJournal takes no responsibility for the information found in this document.

The DNS Cache stores information on the IP address that any given domain or subdomain points to. This is separate from your browser's cache of visited pages. Emptying your DNS Cache will force your computer to request updated DNS information. However, as your Internet Service Provider may also have cached DNS information, it may take up to approximately 48 hours to receive fully updated DNS information after a change has been made.

To empty your DNS Cache:

1. Open the Command Prompt or Terminal. If you are unsure how to do this, it is explained in the [linked] tutorial.

Windows 2000/XP/Vista:
2. Enter ipconfig /flushdns

Macintosh OS X:
2. Enter lookupd -flushcache

Macintosh OS X 10.5 (Leopard):
2. Enter dscacheutil -flushcache

Linux:
2. Restart the nscd daemon by entering /etc/init.d/nscd restart


Create 'Troubleshooting with nslookup, traceroute, and ping'

DISCLAIMER: This document is not an official LiveJournal document. It is a resource document maintained by a fellow user. The original source of information is noted, where available. LiveJournal takes no responsibility for the information found in this document.

To retrieve DNS lookup information:

1. Open the Command Prompt or Terminal. If you are unsure how to do this, it is explained in the [linked] tutorial.

2. Type nslookup livejournal.com. If requested, you may also need to lookup subdomains, such as nslookup l-stat.livejournal.com or nslookup community.livejournal.com.

3. If necessary, copy the information (including the original command) into a text editor, email, or support request. If you are unsure how to do this, it is explained in the [linked] tutorial.

To retrieve traceroute information:

Windows 2000/XP/Vista

1. Open the Command Prompt. If you are unsure how to do this, it is explained in the [linked] tutorial.

2. Type tracert www.livejournal.com and press the Enter or Return key. This process may take several minutes to complete. If requested, you may also need to traceroute to subdomains, such as tracert l-stat.livejournal.com or tracert community.livejournal.com.

3. If necessary, copy the information (including the original command) into a text editor, email, or support requset. If you are unsure how to do this, it is explained in the [linked] tutorial.

Mac OS X or Linux

1. Open the Command Prompt or Terminal. If you are unsure how to do this, it is explained in the [linked] tutorial.

2. Type traceroute www.livejournal.com and press the Enter or Return key. This process may take several minutes to complete. If requested, you may also need to traceroute to subdomains, such as traceroute l-stat.livejournal.com or traceroute community.livejournal.com.

3. If necessary, copy the information into a text editor, email, or support request. If you are unsure how to do this, it is explained in the [linked] tutorial.

To retrieve ping information:

Windows 2000/XP/Vista

1. Open the Command Prompt. If you are unsure how to do this, it is explained in the [linked] tutorial.

2. Type ping www.livejournal.com and press the Enter or Return key. This process may take several minutes to complete. If requested, you may also need to ping subdomains, such as ping l-stat.livejournal.com or ping community.livejournal.com.

3. If necessary, copy the information (including the original command) into a text editor, email, or support request. If you are unsure how to do this, it is explained in the [linked] tutorial.

Mac OS X or Linux

1. Open the Command Prompt or Terminal. If you are unsure how to do this, it is explained in the [linked] tutorial.

2. Type ping -c 10 www.livejournal.com and press the Enter or Return key. If requested, you may also need to ping subdomains, such as ping -c 10 l-stat.livejournal.com or ping -c 10 community.livejournal.com.

3. If necessary, copy the information (including the original command) into a text editor, email, or support request. If you are unsure how to do this, it is explained in the [linked] tutorial.

[general], @ status-resolved

Up