consider that the DNS request packet has a destination address of the server of your former ISP. what you are trying to accomplish, if I understand you correctly, is to change that destination address. Policy routing can change the next hop, but it cannot change the destination IP of the packet in question.
why not leave well enough alone? is there any reason DNS is not being answered by the servers of your former ISP? Do they filter DNS requests from sources not in their space? If not, everyone is happy. If so, then your choices are to visit each machine and physically change the DNS information, or to set up DHCP, and then visit each machine to physically set up DHCP on them. Chuck ""Michael Hair"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I was wondering what is the best way to take care of the following: > > I have been using a private address space behind a Cisco 4500 router > connected up to our current ISP using NAT, now we want to move our > connection from our current ISP to a new ISP with better bandwidth. My > problem is that we don't want to change all our client machines TCP/IP > settings, which are all static, for some reason or another they were all > setup to use our ISP's DNS. Not my idea but that another problem. So how can > I setup our router to forward requests looking from our current ISP's DNS to > our new ISP's DNS without touching all the client machines. > > Would the best way be to use policy-base routing? > > Would a static route work? > > Could I use a static route under NAT? > > If someone could proved me a sample of how you could do this I would be > greatful... > > Thanks > Michael Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=35704&t=35703 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
