DNS resetting

[boden]

I have a small home network consisting of a few XP Pro machines, a Win2K
machine, a demoted Server 2000 machine and a server running Server 2003.

I access the internet through a NetGear RT-311 Router that points to my
ISP's two external AT&T DNS servers, 12.27.189.x. My internal DNS
resides on my 2003 Server. I have looked at all machines and edited all
of the registries to show my internal DNS address in

HKLM>System>Services>TCPIP>Parameters> DHCPNamesServer AND in

Interfaces>[key

name]>DHCPNameServer
(or the equivalent location in Win2K)
correctly.

After a period of time I will no longer be able to browse between
machines with Windows Explorer and upon looking I find that the
DHCPNameServer has reverted back to the value of my ISP's external DNS.
This has happened several times during the past few days.

I'm suspicious that this is because I have a DNS setup error on my
server, but I can't figure out how to correct it. I'd appreciate any
advice.

Thanks,
Boden

 

[Herb Martin]

I have a small home network consisting of a few XP Pro machines, a Win2K
machine, a demoted Server 2000 machine and a server running Server 2003.

I access the internet through a NetGear RT-311 Router that points to my
ISP's two external AT&T DNS servers, 12.27.189.x. My internal DNS resides
on my 2003 Server. I have looked at all machines and edited all of the
registries to show my internal DNS address in

HKLM>System>Services>TCPIP>Parameters> DHCPNamesServer AND in

Interfaces>[key

name]>DHCPNameServer
(or the equivalent location in Win2K)
correctly.

After a period of time I will no longer be able to browse between machines
with Windows Explorer and upon looking I find that the DHCPNameServer has
reverted back to the value of my ISP's external DNS. This has happened
several times during the past few days.

The router is likely sending the ISP DNS to your clients.

You must stop it from doing that -- either by configuring it to give out the
INTERNAL DNS server (only) OR if that is not possible by disabling this
DHCP server and using you real Windows as the DHCP server.

These little routers are frequently difficult to configure for a server
based
network and their DHCP must just be turned off.

I'm suspicious that this is because I have a DNS setup error on my server,
but I can't figure out how to correct it. I'd appreciate any advice.

Fix the DHCP.

 

[Guest]

Hey, I can't post a new thread? Oh, well.
Here is my dilemma, and I have searched and searched the Microsoft resourses
pages, and this group.

I am installing a new server, Active Directory, 2003, as a DC. I have
existing NT 4 service pack 6 PDC. Am migrating to new server. I have an
existing Windows 2000 Terminal Service server that runs DHCP and local DNS to
resolve to its IP for e-mail. Since I will be forming a new domain, I am
concerned that DNS for mail will get hosed/need direction and that DHCP on
our new Active Directory 2003 will not pick up the Imail address. Any
pitfalls that I should be aware of? I have no application software to
transfer, nothing but users and e-mail.

Could someone please help? I've read and read and read....