I Hate DNS....
-
mainly because I haven't got a clue how it works. I have a small (8 client) home network with one windows 2000 server. I also have ADSL with a dynamic IP address (actually never changes). My network is on 192.168.0.x with each client given an IP address through the DHCP server on the ADSL router. The ADSL router and Win2K server have static IPs within the 192.168.0.x range but not in the same scope as the DHCP. Clear so far? At present the clients are all configured with their gateway as the ADSL router and their DNS servers as the ISP's DNS servers. This is a bit diodgy as in theory the Win2k server should be set up as the primary DNS and then delgate any requets it can't handle to the ISP's DNS servers but I couldn't figure out how to do that :-O (any help much appreciated). Anyway, I get home today and my client machines can't connect to the internet. More exactly, they can't resolve the host names into IP addresses. Using IP addresses is OK. What makes it wierd is that the Win2K server can still resolve hostnames fine. The only real difference between this machine and the clients is that it has a static IP. The DNS servers are setup the same as the clients. Anyway, does anyone have some idea about what I should do to fix this? Cheers James
-
mainly because I haven't got a clue how it works. I have a small (8 client) home network with one windows 2000 server. I also have ADSL with a dynamic IP address (actually never changes). My network is on 192.168.0.x with each client given an IP address through the DHCP server on the ADSL router. The ADSL router and Win2K server have static IPs within the 192.168.0.x range but not in the same scope as the DHCP. Clear so far? At present the clients are all configured with their gateway as the ADSL router and their DNS servers as the ISP's DNS servers. This is a bit diodgy as in theory the Win2k server should be set up as the primary DNS and then delgate any requets it can't handle to the ISP's DNS servers but I couldn't figure out how to do that :-O (any help much appreciated). Anyway, I get home today and my client machines can't connect to the internet. More exactly, they can't resolve the host names into IP addresses. Using IP addresses is OK. What makes it wierd is that the Win2K server can still resolve hostnames fine. The only real difference between this machine and the clients is that it has a static IP. The DNS servers are setup the same as the clients. Anyway, does anyone have some idea about what I should do to fix this? Cheers James
-
mainly because I haven't got a clue how it works. I have a small (8 client) home network with one windows 2000 server. I also have ADSL with a dynamic IP address (actually never changes). My network is on 192.168.0.x with each client given an IP address through the DHCP server on the ADSL router. The ADSL router and Win2K server have static IPs within the 192.168.0.x range but not in the same scope as the DHCP. Clear so far? At present the clients are all configured with their gateway as the ADSL router and their DNS servers as the ISP's DNS servers. This is a bit diodgy as in theory the Win2k server should be set up as the primary DNS and then delgate any requets it can't handle to the ISP's DNS servers but I couldn't figure out how to do that :-O (any help much appreciated). Anyway, I get home today and my client machines can't connect to the internet. More exactly, they can't resolve the host names into IP addresses. Using IP addresses is OK. What makes it wierd is that the Win2K server can still resolve hostnames fine. The only real difference between this machine and the clients is that it has a static IP. The DNS servers are setup the same as the clients. Anyway, does anyone have some idea about what I should do to fix this? Cheers James
Change the setup... DSL -> Router -> server_external_nic -> server -> server_internal_nic -> Hub -> clients Keep the external networjk set up as the same subnet that teh router wants to use (192.168.0.1 or 10.0.0.1 are popular). Give all clients a static IP address (you only have 8 clients so that should not be tooo hard). Read up in the NT userguide for NAT. Set up your own local DNS (you will have to do this if you use Active Directory to authenticate clients anyway) and set the forwarders of that server to your ISP DNS servers. Basically this is the best way to set up.. you can use the server as a secondary router and authenticate all your users off of it. I use the setup in my home office with a cable internet conneciton and it works great. I run a copy of Microsoft Small Business Server 2000 (Exchange, ISA Server, SQL, the works) and things run fantastic.
-
Has the Win2k server been running continuously? It caches any DNS searches and uses the cached addresses if it can't connect to the ISP's servers.
It has been running continuouslybut I just tested this theory by putting in a few web addresses that I've never been to before and it found them straightaway. Must be something else... Cheers James