At 09:09 10/01/2003 -0500, Hal MacArgle wrote: >Greetings: Contemplating an ISP change I thought I'd ping the present >thence the proposed DNS's to evaluate the round trip time.. > >The present, 204.97.4.2, returned it's RTT to be expected.. The >proposed, 65.196.16.3, returned "100% packet loss" - not expected. > >Both addresses are in /etc/resolv.conf, but that shouldn't make a >difference here - IMHO. <grin> Also; since I'm connected to the INet >via the present ISP my ping testing idea might be a dumb one. > >Invoking 'dig' for both addresses I find a difference in the report: >"ANSWER" is set = 1, on the working site and = 0 on the non-working. >This is obvious, to me, what's happening but I can't help but >wonder if that might mean I wont be able to use that site? /Or/ why >would a SysAdm set his/her site to not support ping? I'm confused. > >TIA and thanks, > > Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0 (2.4.13) > [EMAIL PROTECTED] | [EMAIL PROTECTED] > Proprietary Formats Unacceptable >. >- >To unsubscribe from this list: send the line "unsubscribe linux-newbie" in >the body of a message to [EMAIL PROTECTED] >More majordomo info at http://vger.kernel.org/majordomo-info.html >Please read the FAQ at http://www.linux-learn.org/faqs
Are you sure the new DNS ip is correct (65.196.16.3). I tried dig and could only find that it was an address assigned to uunet and nothing else. ping and traceroute both tell me the "net is unreachable". -- Carl - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
