Folks,
I have successfully configured my network so that it will dial-on-demand the local ISP
whenever anyone wants to access a site outside the local network. I am using
NAT/IP-Masq to connect my network to a single simple "unlimited hours" dialup account.
All works well (ftp, www etc).
Now, I have a couple of questions. I have an internal domainname and internal domain
name servers. I want to know how this will effect resolving external domain names.
Correct me if I am wrong but if the local DNS cannot resolve the name/IP address then
it should contact the next level authoritive server (which will bring up my link).
IE: If I want to resolve slug.org.au then the DNS would contact the com.au name
server. Since it does not know this either, it would contact .au and since it does
not know this, it will eventually contact one of the root servers that are listed in
the zone files and work back down.
Now reading up on DNS, it tells me that the DNS server needs to regularly contact
these root servers. So what does this mean for a DNS that is not permanently
connected to the internet - I don't really want my dialup link flapping up and down
every couple of hours just to do a DNS update - the phone bill would go through the
roof.
What do people suggest ???
As far as the resolving goes, all resolutions end up in the DNS cache but how long do
they stay there - and what is the best expiry time for this ???
Now all I got to do is get the mail working over a dial-on-demand line ... That will
be my next challenge.
Matt
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
