Search Again: Slaves, and recursive... From: Jerry Pasker Date: Tuesday, April 6, 1999 Time: 7:08:00 am Ok, here's a question that I've been playing with in my mind, for quite some time now: Picture this, picture this, here is the scenerio... I'm an ISP, running two QuickDNS Pro servers, for roughly 1000 end users. Most of my end users are set to automatically get their DNS numbers from my terminal servers, when they log in, and this works great. If I change my IP numbering scheme, and IP numbers of my DNS servers, it's not an issue, because I can just assign the new numbers to people, when they log in, all without them knowing a change ever took place. I am looking at possibly changing upstream ISPs in the future, and would like to keep my options open. Some people use Windoze 3.11, and versions of the MacOS prevoius to 8.5, that do not get their DNS numbers from my terminal servers. These clients must have their DNS numbers entered [changed] manually. This is a bad thing. If I renumber my network, I'll have to change DNS IP numbers, and it is going to be a problem to renumber all the people that are using the old DNS numbers. Here's my idea/question: Is it possible to retain a DNS server on my network, with an old IP number, running in slave forwarding mode to my new DNS servers, if my boarder router knows that the IP number of one my of "old DNS servers" is on my local network? Is this how packets would flow arround my netowrk? I know how to make my routers route properly (acutally, this would be kind of breaking the rules) so getting the routers to move packets isn't a problem. However, it introduces the problem that certain machines won't be able to talk directly to other machines. Client computer: Can talk to entire Internet, including New DNS server, and Old DNS server. New DNS server: Can talk to entire Internet, including end client computers, and even the old DNS server Old DNS Server: Can NOT talk to global Internet, but CAN talk to new DNS server, and client computers. This server would be opertaing in slave mode, and would send all requests onto the new DNS server, that would resove them, and send them back. Here's how the datagrams would flow: Request for name lookup, destination "Old DNS Server" router traps, and sends udp packet to the old DNS server old DNS server quirries new DNS server, sends datagram to router router redirects datagram to newer DNS server Newer DNS server goes out to the net, does DNS lookup, and sends a response back to the "old DNS server" router traps reponse packet, and sends it to the old DNS server Old DNS server sends response to client router directs packet to client IP address Would this work?

Messages In This Thread: Slaves, and recursive... by Jerry Pasker on Apr 6, 1999 at 7:08:00 am Re: Slaves, and recursive... by Chris Buxton on Apr 6, 1999 at 12:28:00 pm