Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I'm really stumped on this one. We have a small business, and we had a bunch of pieced together windows 2000 machines with file sharing. We wanted to slowly change over to a single 2003 server, but we couldn't have downtime, so we did it slowly. Now we have changed everything over (mainly file sharing), but now were trying to create our domain and make clients connected to it since some people are sharing workstations. We set it up as a DNS server, and we made the first record on the machine for DNS the machine itself x.x.x.204, and then the second dns our gateway, x.x.x.1 - so when we setup clients, we set the primary dns as the x.x.x.204 (our server), but they receive a dns error when trying to connect to the server. Any help would be appreciated!

"We set it up as a DNS server, and we made the first record on the machine for DNS the machine itself x.x.x.204, and then the second dns our gateway, x.x.x.1"
That is not a proper configuration.
First off, be careful of your terminology. Records mean entries within DNS itself that it can respond with for an answer. Examples:
A record
PTR Record
NS record
SOA recordI *assume* you mean you set up the IP's used for primary and secondary DNS servers the DC will use.
If that's the case, that is an incorrect configuration. The DC/DNS server should be pointed to itself only for DNS. If your router acts as a DNS server for internet access, then you should configure the DC/DNS server to use it as a forwarder.
TECH-NO-LOGICAL ROMANCE!
http://www.homestarrunner.com/tgs12.html

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |