Windows Forum

Ask something
Discussion Locked

ipconfig/registerdns

0 helpful
2 replies

by jroberts

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are a small orginization running Small Business Server 2000 using an Active Directory Domain. We also run a web Server that is not on the domain but in a work group. We run 3 web sites on the one web server with three distinct IP addresses bound to one external nic. We have active directory integrated DNS running on the Small Business Server.

Our Web server has two nics one is the external with 3 static public IPs and the other is internal which has a valid static internal network IP. We have configured the external nic to not register DNS and it uses our ISP's servers to resolve names.

Our problem lies in the fact that we seem to totally loose contact with our web server's external addresses once every couple of days. We then have to run the command line utility "ipconfig/registerdns". It is very sporadic, yet when we loose contact with our web server, it won't even let us in using terminal services with a specific external IP address. What we do is terminal into our Domain Controller and then terminal using a client on the DC to get to the internal nic on the web server. We then register DNS and then we can see it again.

Help!

2 replies

by dynamo2003

You need to setup a downstream caching only DNS server is possible by so doing the local DNS server contacts your ISP's DNS if it need be then there won't be loss of contact with your ISP's DNS server. You can create a secondary DNS on site to pointat your ISP's on the Internet.

A caching only name server is a Domain Name System (DNS) Server that is not authoritative for any particular domain. Its only function is to look up names for clients and cache them.

After a period of time, as names are resolved, the cache will be populated with the most frequently requested names, and these names/addresses are available quickly for subsequent queries.

A caching-only DNS server may be valuable at a site where DNS functionality is neededlocally but there is not a requirement for a separate domain for that location. This will reduce the amount of DNS traffic on a Wide Area Network (WAN), as the DNS cache may be able to satisfy many of the queries locally.

by jroberts

I think the submitted answer suggesting that we set up an additional (physical) DNS server on the WAN. Making this a caching only server. I don't see how this will solve the problem and I don't understand why additional servers are required. How does this prevent our Web server from being unaccessable from the outside? We already have our ISP DNS server pointing at the Web Server in our DMZ. Our web server seems to be making the decision after a period of time that all connections from the outside including Terminal Services are cut off. Why is it doing this? Why does registering DNS solve the problem temporarily?

This discussion is closed to new replies.