Re: DNS Problem?? Help!!

From: the confused (anonymous_at_discussions.microsoft.com)
Date: 03/18/04 

Date: Thu, 18 Mar 2004 07:21:07 -0800

For your curent set up, I would use the dns server as the
primary dns for your clients, and remove the root zone as
kevin mentiioned, and then set up a forwarder (the
router, 192.168.0.1) and use the root hints (from MS
directly or from the dns directory).

Then local resolution will be done from the zones hosted
on the server, and nonlocal names will be resolved by the
ISP's dns through the router ...

>-----Original Message-----
>Ip addresses for the Dns servers at the ISP are static
addresses, they are
>configured in the DSL modem. The router does do NAT,
the ip addresses from
>the router are 192.168.1...... The IP address for the
server is static, and
>I excluded it from DHCP in the router.
>"the confused" <anonymous@discussions.microsoft.com>
wrote in message
>news:aa5f01c40c97$ab07d9f0$a001280a@phx.gbl...
>>
>> where do you get your IP addresses? or you are using
>> static ones?
>>
>> what is your Linksys router capable of? does it do
NAT?
>>
>> >-----Original Message-----
>> >Have a problem at a client site. Installed Windows
2003
>> Server, using
>> >active directory. Internet access is through a DSL
>> modem. They currently
>> >are using a Linksys router connected to the hub. The
>> ISP uses static IP
>> >addresses in their modem.
>> >
>> >Clients are pointing to the Windows 2003 Server IP
>> address for DNS. On the
>> >server I have the IP address of the server for DNS, as
>> well as the DNS IP
>> >addresses from the ISP.
>> >
>> >Three workstations accessing a database on the network
>> have slow access, and
>> >application stops responding, but one of the
>> workstations does not have a
>> >problem.
>> >
>> >It seems that the workstations began having the
problem
>> after I added the
>> >ISP's addresses to DNS and rebooted the server, but
why
>> did it not effect
>> >the 1 workstation.
>> >
>> >I have been reading other posts about using
forwarders,
>> how is that done,
>> >and is it necessary in this case?
>> >
>> >I am very frustrated!
>> >
>> >Thank you for your help in advance!
>> >
>> >Candace Sparks
>> >
>> >
>> >.
>> >
>
>
>.
>

Relevant Pages

  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... You say "And in the router you need to forward to your external nic IP" ... You say "You need the domain hoster to setup a DNS record that will be ... We have rerun CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)