![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| IP Networking Learn TCP/IP, Internet Protocol, Routing, Routers, Network protocols in this UNIX and Linux forum. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| testing | lcharles | UNIX for Dummies Questions & Answers | 0 | 10-23-2007 12:36 PM |
| testing | areef4u | UNIX for Advanced & Expert Users | 1 | 08-04-2006 08:04 AM |
| testing | areef4u | UNIX for Advanced & Expert Users | 2 | 08-02-2006 12:01 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
an effective to way to test dns is to
use nslookup the syntax is nslookup domainname or ip address examlpe is nslookup www.yourdomainname.com this will query yourdomainname dns and return an ip address. or nslookup (ip address of your dns) this will query yourdomainname dns using an ip address and return full domainname dns is important for web base mail without it you will not be able to received or sent email outside your network or domain. |
|
||||
|
use dig
Assuming you have a caching nameserver, as said above use dig
Test your nameserver using host or dig and querying redhat.com Quote:
From the above dig query you can see it took 42 msec to receive the DNS request. Now test out the caching ability of your nameserver by running dig again on the redhat.com domain. We dropped from 42 msec to 1 msec after the previous DNS query was cached. Caching is working! |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|