C
Chris
Saw some problems remotely like this using a google search
(mainly folks needing to configure a forwarder but I have
already done that!) of the group but if this is a post
that repeats a previous one, please accept my apologies in
advance.
Rolling out a new server here... (running W2K Server).
The server is a primary domain controller, has been
promoted, and DNS is installed. This is for a software
development lab that has a small number of clients
attached its domain. There is no ISP for internet access
but we will be "tapping" onto the corporate pipe to get
out to the internet (needed only to retrieve software
patches, drivers, do limited research, etc... the internet
is not central to our development area). Our domain is
local and not registered. Also, I'm running SP3, dynamic
updates are set to "Yes", and I deleted the "." forward
lookup zone.
1. On the server, the IP address of the box and the
preferred DNS server is the same.
2. On the clients, they have their own statically
assigned IPs and all of their preferred DNS server
addresses is the IP address of the server.
3. On the sever, in DNS, I have a forwarder enabled that
uses a reserved IANA address for external resolution
(again, I don't have an ISP, nor am I registered, so when
one of the boxes wants to access the outside world, it
needs something to lookup its request).
Using that config, I can access the internet from all of
the clients but not the server. If I take the forwarder
out, I cannot access the internet from anywhere; add the
forwarder back and voila' the internet is accessible for
the clients but still not the server.
Any suggestions why the server cannot get out to the
internet but the clients can (and the clients point to the
server for DNS afterall)?
Thanks,
--Chris
(mainly folks needing to configure a forwarder but I have
already done that!) of the group but if this is a post
that repeats a previous one, please accept my apologies in
advance.
Rolling out a new server here... (running W2K Server).
The server is a primary domain controller, has been
promoted, and DNS is installed. This is for a software
development lab that has a small number of clients
attached its domain. There is no ISP for internet access
but we will be "tapping" onto the corporate pipe to get
out to the internet (needed only to retrieve software
patches, drivers, do limited research, etc... the internet
is not central to our development area). Our domain is
local and not registered. Also, I'm running SP3, dynamic
updates are set to "Yes", and I deleted the "." forward
lookup zone.
1. On the server, the IP address of the box and the
preferred DNS server is the same.
2. On the clients, they have their own statically
assigned IPs and all of their preferred DNS server
addresses is the IP address of the server.
3. On the sever, in DNS, I have a forwarder enabled that
uses a reserved IANA address for external resolution
(again, I don't have an ISP, nor am I registered, so when
one of the boxes wants to access the outside world, it
needs something to lookup its request).
Using that config, I can access the internet from all of
the clients but not the server. If I take the forwarder
out, I cannot access the internet from anywhere; add the
forwarder back and voila' the internet is accessible for
the clients but still not the server.
Any suggestions why the server cannot get out to the
internet but the clients can (and the clients point to the
server for DNS afterall)?
Thanks,
--Chris