But nslookup performs a different function. In fact, dig does even more
and when I run nslookup around here on my slackware 8.0 box, it mentions
that nslookup may be going away and encourages one to use dig instead.
nslookup and dig simply query the name server. Pings actually try and
connect or address with the destination desired.
On Mon, 4 Mar 2002, George Toft wrote:
> nslookup provides far more information and works even if
> ICMP packets are blocked.
>
> George
>
>
> Digital Wokan wrote:
> >
> > FYI and for others who have seen similar, the best tests of connectivity
> > involve pinging a known IP address (that doesn't block pings). If you
> > can ping an address, but can't get to its www.blah.com address, you have
> > DNS issues.
> >
> > Lee Einer wrote:
> > >
> > > Thanks, Ed-
> > >
> > > You're a prince among men. I plugged in the new DNS numbers you
> > > suggested, and I now have connectivity with the internet through Linux
> > > once more. I don't have a router box- mine is just a stand-alone PC.
> > > Is there a way for me to detect the correct DNS numbers if Cox decides
> > > to change things again in the future?
> > >
> > > Thanks again, and thanks to all who responded to my post.
> > >
> > > Lee Einer
> > >
> > > Ed Cernek wrote:
> > >
> > > > This may not apply to you, but I, too, had COX problems this
> > > > morning. I was able to solve it by changing my dns'. The old ones
> > > > were 24.1.240.x. My LinkSys router box, which is dhcp to COX, now
> > > > reports the dns as 68.2.16.30 and 68.1.208.30. I plugged these in
> > > > and it worked like a charmEd.
> > > > -----Original Message-----
> > > > From: plug-discuss-admin@lists.plug.phoenix.az.us
> > > > [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of Lee
> > > > Einer
> > > > Sent: Saturday, March 02, 2002 07:45
> > > > To: plug-discuss@lists.plug.phoenix.az.us
> > > > Subject: Problems with DHCPCD and Cox.net
> > > >
> > > > Hi, all-
> > > >
> > > > I am a linux newbie (2 years experience) living here in Phoenix. I
> > > > run a dual boot with Corel Linux 2nd edition and Windows 98. I am
> > > > regrettably posting to you from the Windows side, as I am now unable
> > > > to connect to the intranet using Linux.
> > > >
> > > > I had no appreciable problems connecting until yesterday. I have
> > > > verified that DHCPCD is still starting at boot-up and is running.
> > > > Ifconfig shows that the network connection is up, and the ip
> > > > addresses look valid to me, although on one or two occasions when I
> > > > have run it the RX line shows that a large amount of data has been
> > > > dropped. I am no whiz at this, but I think that I have tried the
> > > > most obvious, such as killing DHCPCD and then restarting from a
> > > > command line with -r, -h, etc--, renaming the resolve.conf file,
> > > > shutting off power to the modem and then restarting the modem, all
> > > > without success. I am at wit's end here, I hate using Windows, and
> > > > I want my Linux back.
> > > >
> > > > Is anyone else having these blues? I thought it odd that this
> > > > happened on the day after Cox supposedly terminated any vestiges of
> > > > @home service (e-mail, etc.) I would appreciate any help/advice you
> > > > can give on troubleshooting and fixing this problem.
> > > >
> > > > Thanks,
> > > >
> > > > Lee Einer,
> > > > Phoenix, AZ
> > > >
> > > > http://members.cox.net/appealsman
> > ________________________________________________
> > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> >
> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
(text/plain)