I could not disagree with willcomp more. In any 2000 or 2003
network, DHCP should be on the server. many small business' do
do it his way, but that is only because of a lack of knowledge,
not because it is good design. Any XP or 2000 clients look for
logon servers and AD service info in DNS. They may even try to
register themselves in DNS. If the DHCP is the router then it will
assign ISP DNS servers and you will generate many errors in
logs. Put DHCP on the server and config options for DNS, Wins if
needed, gateway etc.
I do not know what you are trying to acomplish, but since you
said "test 2k server" I will make some guesses.
When you say "seems to always fail when I am setting up DNS",
what does it say, do, or log?
I will assume the following:
1. You know that you are using public ip's.
If your server is behind a firewall / router then it should be a
private ip. Something like 192.168.y.z or 10.x.y.z. Even if it is
public, there are advantages to it being screened. If it needs for
some reason to be public then you're ok but it should still be
behind the firewall, maybe on an Optional Port, to stop Dos
attacks etc. (I do not know why a test server would be public
though).
Now, Why do you want to use a public domain name of
BTN.com? If it is the public server then have the domain point at
the router public ip and keep the internal DNS/DOMAIN as
BTB.local. Using a .com internally will cause issues with external
resolution of that domain.
I usually set routers at .1, .2 etc up to whatever. Servers are .10,
.11 etc and workstations in the .100's. Network printers in the
.200's but that is subjective.
Run DC Promo and let it setup DNS. Do not choose to be a root
serverIf it sets up as a root then go into DNS and delete the "."
entry. Then the root hints will function and you could even set
forwarders to the ISP DNS servers.
DNS can be complex, but in a single 2000 domain it should auto
se