Re: ping

From: Jeroen Geilman (nospam_at_notadaptr.nl)
Date: 10/21/03 

Date: Tue, 21 Oct 2003 18:16:14 +0000

Sachin <linux_man_ind@yahoo.com> randomly warbled in comp.os.linux:

First off, I doubt that you wanted to reply to Michael's post.

> either try these command
> man hosts
> man nslookup
> man dig

Why ?

He named his post "ping", didn't he ?

"man ping" would seem, to me, to be more appropriate here.

> dig is the best one

...for what, exactly ?

> if your dns server is perfect and have an entry for both the forward
> and backward lookup.

? what does that mean ?

As long as *a* nameserver somewhere has the correct entries it'll work
just fine...

> then type this comand
>
> 1. dig <our ip address of the dns server>

That's not even a command, dude...

> if this works fine then try this
> Note :- if client RR entry at dns server

Which client ? Which nameserver ?

> dig <cliient ip address>

I'd start with this :

#dig -x ip.add.re.ss

And see what you get. 

-- 
Jeroen Geilman
All your bits are belong to us.

Relevant Pages

  • Re: NDR to ONE domain only
    ... Telnet to your ping result IP on port 25 and report back to us! ... lyo-t.com NS (Nameserver) ns3.paetec.net ... lyo-t.com MX (Mail Exchanger) Priority: ... My nslookup results from an XP command prompt: ...
    (microsoft.public.windows.server.sbs)
  • Re: How to resolve names
    ... So I can ping and try to ssh/telnet the 2 other machines from my PC via ... name/address resolution via nslookup. ... use dig instead, but its brokenness does not extend to returning answers ...
    (comp.os.linux.networking)
  • Re: slow start
    ... Should I be able to ping all the ntp servers in my /etc/ntp.conf? ... You should not, however, start your troubleshooting by pinging your NTP servers. ... Don't use nslookup, use dig. ... I suggested nslookup, rather than dig, because nslookup is installed on both Solaris and Windoze and I think Linux as well. ...
    (comp.protocols.time.ntp)
  • resolve hostname
    ... I can ping the outside ipaddresses but not the hostnames on my solaris ... nameserver 68.87.72.130 ... ipnodes: files dns ... alpine# nslookup www.google.com ...
    (SunManagers)
  • Dig and nslookup resolve; ping doesnt
    ... I'm able to resolve ... names such as www.yahoo.com using nslookup or dig but not using ping. ...
    (comp.os.linux.networking)