hey mrhoffman, thanks so much for the interest in this topic!
Can the guest network route IP to the private network? (That's not usually the case, after all.)
nope, the guest network can not reach the private network. this is what apple says, and i can verify from experimentation, however, the routing table in the APE is not accessible ... at least, i don't know how to access it. nor do i really want to, separate networks is what i want.
I don't know off-hand if the Airport Extreme can have two sets of DNS servers, one for private and one for the guest LAN.
there is no obvious way of doing this ... of course, for me, that would be the best solution here!
And I'd tend to keep away from having ISP DNS and local DNS in the same client configuration as you might not be getting your translations from where you think you're using.
i see. duplicate internal DNS servers is a bit overkill for me, so i think removing the ISP DNS from the configuration would be preferred for my private network; then handling downtime appropriately ... i.e. server reboot!
but, that leaves the guest network out in the cold.
the technical part i still don't understand is what happens to the DNS request once it gets to the APE. my guest client thinks that the APE is the DNS server, it doesn't know about the internal server. it is the APE that thinks my internal server is the DNS server ... alternatively, it thinks that the ISP server is a secondary option (which after your remarks will be changed). so, when the guest client asks the APE for a DNS lookup, what happens? does the APE try to
forward the client to the internal server and cause the routing issues you described? or does the APE then make a request itself to the internal server as a
proxy? the thing that is causing this confusion for me is that when i look at the guest client's DNS server, it is the APE and
not my internal server (however, when a private client connects, its DNS server
is the internal server).
i appreciate your help and knowledge,
b