In message <eadf127e4f.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx> Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > In message <1fbf0c7e4f.GrahameParish@xxxxxxxxxxxxxx> > Grahame Parish <grahame.parish@xxxxxxxxxxxxxxx> wrote: > >> In message <Marcel-1.53-0310110652-1cbpErr@xxxxxxxxxxxxxxxxxxxxxx> >> Chris Evans <chris@xxxxxxxxxxxxxxx> wrote: > >>> >>> You can also manually set the the DNS in each computer with the DNS quoted >>> by your ISP. >>> >> But don't make your ISP's DNS the main one if you also need to resolve >> internal addresses. Set the internal network DNS as the first to >> check, followed by the ISP's DNS as the secondary (and tertiary if >> they give you two DNS addresses). > > Are you thinking of a local network with a real DNS server? i.e. not > using the router as a DNS relay? > > In such a case the internal DNS server needs to have forwarders > configured for the external DNS servers. > Yes, this is the best approach for this situation. When I first set up my network I put the ISP DNS first and wondered why it took a long time to boot up the machines when the Internet connection was down. :( > [snip] > > The local real DNS server situation is different. Here the client > queries the local server always. If the local server doesn't know the > answer it forwards the query, and caches the reply for future use. > Such a real DNS server is likely to be running on Linux or Windows > server edition. > As here (Windows Small Business Server 2003). -- Grahame Parish grahame.parish@xxxxxxxxxxxxxxx --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support