sorry me again, I think I know why my router can't query the DNS. The reason is when I do a extended ping as follow, it tried to query the DNS server for real IP with the source address of the serial0 (default) before we can specify to use ethernet0 as the source address. And ISP never advertise route for the serial link. That's why I can't query the DNS. How do you think??
>2500new#ping >Protocol [ip]: >Target IP address: www.channelnewsasia.com >Translating "www.channelnewsasia.com"...domain server (203.116.1.93) >(203.116.254.150) > >% Bad IP address >From: "Kenny Smith" >Reply-To: "Kenny Smith" >To: [EMAIL PROTECTED] >Subject: Re: why I can't use normal ping in new router??? [7:43709] >Date: Fri, 10 May 2002 02:58:45 -0400 > >Thanks.. Priscilla.. I understamd what you mean about the route issue and I >think it is right. But I have one more issue. That's the DNS. I >tried to test whether new DNS is working or not with the following. But it >always give me Bad IP address, but the DNS IP is proven to be working when >we put it to our proxy. Beside, when I do the same thing in my old router, >it did get translated. Why my new router DNS can't resolve my URL while >the >DNS is proven to be to working fine?? > >2500new#ping >Protocol [ip]: >Target IP address: www.channelnewsasia.com >Translating "www.channelnewsasia.com"...domain server (203.116.1.93) >(203.116.254.150) > >% Bad IP address > >2500old#ping >Protocol [ip]: >Target IP address: www.channelnewsasia.com >Translating "www.channelnewsasia.com"...domain server (210.80.58.205) [OK] > >Repeat count [5]: >Datagram size [100]: >Timeout in seconds [2]: >Extended commands [n]: >Sweep range of sizes [n]: >Type escape sequence to abort. >Sending 5, 100-byte ICMP Echos to 202.172.227.114, timeout is 2 seconds: >!!.!! >Success rate is 80 percent (4/5), round-trip min/avg/max = 196/253/324 ms > > > >From: "Priscilla Oppenheimer" > >Reply-To: "Priscilla Oppenheimer" > >To: [EMAIL PROTECTED] > >Subject: Re: why I can't use normal ping in new router??? [7:43709] > >Date: Thu, 9 May 2002 17:17:19 -0400 > > > >Would upgrading solve his problem? > > > >At 03:00 PM 5/9/02, Larry Letterman wrote: > > >I didn't say 10.3 would not handle it, did I...I just said to update >the > > >ios because its old... > > > > > >Larry Letterman > > >Cisco Systems > > >[EMAIL PROTECTED] > > >----- Original Message ----- > > >From: "Priscilla Oppenheimer" > > >To: > > >Sent: Thursday, May 09, 2002 10:37 AM > > >Subject: Re: why I can't use normal ping in new router??? [7:43709] > > > > > > > > > > At 03:57 AM 5/9/02, Larry Letterman wrote: > > > > >Update the IOS to something modern... > > > > > > > > Do you work for TAC? Cisco IOS 10.3 could certainly handle ping just > >fine. > > > > ;-) > > > > > > > > I have a guess. Notice that the serial link has a subnet mask of > > > > 255.255.255.252. This is a subnet mask that you typically see on a > > > > point-to-point link with just two devices on it (the routers at >either > > > > end). The link has no purpose other than to connect the customer's >LAN > >to > > > > the ISP. Hence, there's no reason for the ISP to advertise a route >to > >that > > > > point-to-point 100.20.90.56/30 network. In fact, for security >reasons, > > >it's > > > > probably a good idea to make sure there is not a route to this > >dedicated > > > > network that has just two memebers, the two router interfaces. > > > > > > > > So, this means that there's no way for a ping reply to get back to >the > > > > 100.20.90.58 address. > > > > > > > > Now, the LAN is addressed with a network number and subnet mask that > >you > > > > might see used for a typical small customer (60.80.200.113 > > > > 255.255.255.240). Undoubtedly, there are no problems getting back to > >this > > > > LAN. The fact that he can surf the Web proves that point. > > > > > > > > Priscilla > > > > > > > > > > > > > > > > > > > > >Larry Letterman > > > > >Cisco Systems > > > > >[EMAIL PROTECTED] > > > > >----- Original Message ----- > > > > >From: "Kenny Smith" > > > > >To: > > > > >Sent: Thursday, May 09, 2002 12:20 AM > > > > >Subject: RE: why I can't use normal ping in new router??? [7:43709] > > > > > > > > > > > > > > > > Below is my config...why you think there is a route missing > >somewhere, > > >as > > > > >I > > > > > > can still use extended ping to ping and I can use it to surf net > >as > > > > >normal. > > > > > > The only thing that I can't do is to normal ping from here.. >What > > >should > > > > >me > > > > > > the problem? It is related to the new ISP? > > > > > > > > > > > > 2500new#sh conf > > > > > > Using 1561 out of 32762 bytes > > > > > > ! > > > > > > version 10.3 > > > > > > no service finger > > > > > > service password-encryption > > > > > > no service udp-small-servers > > > > > > no service tcp-small-servers > > > > > > ! > > > > > > hostname 2500new > > > > > > ! > > > > > > enable secret xxxxxx > > > > > > ! > > > > > > ip subnet-zero > > > > > > no ip source-route > > > > > > ! > > > > > > interface Ethernet0 > > > > > > description To Office Ethernet > > > > > > ip address 60.80.200.113 255.255.255.240 > > > > > > no ip directed-broadcast > > > > > > ip accounting output-packets > > > > > > ip route-cache same-interface > > > > > > ! > > > > > > interface Serial0 > > > > > > description XXX > > > > > > ip address 100.20.90.58 255.255.255.252 > > > > > > no ip directed-broadcast > > > > > > ip accounting output-packets > > > > > > bandwidth 512 > > > > > > ! > > > > > > interface Serial1 > > > > > > no ip address > > > > > > shutdown > > > > > > ! > > > > > > ip name-server 203.116.1.78 > > > > > > ip name-server 203.116.1.94 > > > > > > ip classless > > > > > > ip route 0.0.0.0 0.0.0.0 100.20.90.57 > > > > > > tftp-server flash \tftpboot\IGS-IN-L.BIN > > > > > > snmp-server community public RO > > > > > > banner exec ^C > > > > > > > > > > > > Router name: 2500new > > > > > > Platform: Cisco 2500 > > > > > > Location: Equant > > > > > > > > > > > > ^C > > > > > > banner login ^C > > > > > > > > > > > > Unauthorised access is prohibited and may lead to > > > > > > legal or disciplinary action being taken against you > > > > > > ^C > > > > > > ! > > > > > > line con 0 > > > > > > line aux 0 > > > > > > transport input all > > > > > > line vty 0 > > > > > > exec-timeout 15 0 > > > > > > password 7 XXXXXXXX > > > > > > login > > > > > > length 0 > > > > > > line vty 1 > > > > > > exec-timeout 0 0 > > > > > > password 7 XXXXXXX > > > > > > login > > > > > > line vty 2 4 > > > > > > password 7 XXXXXXX > > > > > > login > > > > > > ! > > > > > > end > > > > > > > > > > > > > > > > > > > > > > > > >From: Andrew Larkins > > > > > > >To: Kenny Smith , [EMAIL PROTECTED] > > > > > > >Subject: RE: why I can't use normal ping in new router??? > >[7:43709] > > > > > > >Date: Thu, 9 May 2002 08:53:34 +0200 > > > > > > > > > > > > > >my guess is that there is a route missing somewhere here from > >when > > >you > > > > > > >migrated to the new unit. Just to make sure, plse post the > >configs > > >and > > > > we > > > > > > >can see. > > > > > > > > > > > > > >-----Original Message----- > > > > > > >From: Kenny Smith [mailto:[EMAIL PROTECTED]] > > > > > > >Sent: 09 May 2002 07:54 > > > > > > >To: [EMAIL PROTECTED] > > > > > > >Subject: why I can't use normal ping in new router??? [7:43709] > > > > > > > > > > > > > > > > > > > > >May I know why I have to use extended ping/traceroute to ping > >from > >my > > > > new > > > > > > >router (2500new) and I have to specify extended command3yes, >and > > >source > > > > > > >address is ethernet0 (serial0 don!&t work). If I just use ping > > > > > > >202.172.227.114. it doesn!&t works. Why??? And I can use > >!'ping > > > > > > >202.172.227.114!( to ping from my old router (2500old) !Vshown > >below. > > > > > > >Why??? Why I can only use extended ping and specify ethernet0. > > > > > > > > > > > > > >2500new#ping > > > > > > >Protocol [ip]: > > > > > > >Target IP address: 202.172.227.114 > > > > > > >Repeat count [5]: > > > > > > >Datagram size [100]: > > > > > > >Timeout in seconds [2]: > > > > > > >Extended commands [n]: y > > > > > > >Source address: ethernet0 > > > > > > >Type of service [0]: > > > > > > >Set DF bit in IP header? [no]: > > > > > > >Data pattern [0xABCD]: > > > > > > >Loose, Strict, Record, Timestamp, Verbose[none]: > > > > > > >Sweep range of sizes [n]: > > > > > > >Type escape sequence to abort. > > > > > > >Sending 5, 100-byte ICMP Echos to 202.172.227.114, timeout is 2 > > >seconds: > > > > > > >!!!!! > > > > > > >Success rate is 100 percent (5/5), round-trip min/avg/max = > >16/22/40 > > >ms > > > > > > >2500new# > > > > > > >2500new#ping 202.172.227.114 > > > > > > >Type escape sequence to abort. > > > > > > >Sending 5, 100-byte ICMP Echos to 202.172.227.114, timeout is 2 > > >seconds: > > > > > > >..... > > > > > > >Success rate is 0 percent (0/5) > > > > > > >2500new# > > > > > > >2500new# > > > > > > > > > > > > > > > > > > > > >2500old#ping 202.172.227.114 > > > > > > > > > > > > > >Type escape sequence to abort. > > > > > > >Sending 5, 100-byte ICMP Echos to 202.172.227.114, timeout is 2 > > >seconds: > > > > > > >!!!!! > > > > > > >Success rate is 100 percent (5/5), round-trip min/avg/max = > > >44/171/376 > > > > ms > > > > > > > > > > > >2500old# > > > > > > > > > > > > > > > > > > > ________________________ > > > > > > > > Priscilla Oppenheimer > > > > http://www.priscilla.com > >________________________ > > > >Priscilla Oppenheimer > >http://www.priscilla.com >_________________________________________________________________ >Chat with friends online, try MSN Messenger: http://messenger.msn.com _________________________________________________________________ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=43818&t=43709 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
