Windows Forum

Ask something
Discussion Locked

Unwanted DNS Calls from Win2K Server

0 helpful
8 replies

by nordeide

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

I have set up a Win2K server for a small
company. I understand that in order for the
server to act as a DC, I have to install
Active Directory, which in turn requires DNS.

The system consists of an ISDN router with
IP address 192.168.1.1/24,the Win2K server
at 192.168.1.2/24, and the workstations with
192.168.1.3/24 and so forth. All computers,
including the server, has the router as
default gateway and the ISP's DNS servers
set up in DNS under TCP/IP properties, and
all can access the Internet just fine through
the router's NAT service.

But then I found that the server sends a lot
of Internet requests, thus making the router
picking up the ISDN line all the time. This
gave the customers a shocking ISDN bill. Using the Network Monitor, I found that they
are DNS calls. Unfortunately, I do not have
the knowledge to analyse these packets
any further.

The AD is set up with a local domain name
(.local), and the server is not
supposed to contact the Internet except when
the E-mail server (MDaemon v3.5) needs it.

Any ideas out there? As you see, this is a
private network with no need for constant
Internet access, and the local DNS server
is not supposed to synchronise woth the
global DNSes at all.

Any help would be greatly appreciated!

8 replies

by andy_p

Rolf

The DNS setting on the TCPIP properties should never be your ISP DNS. (unlike NT4)

It must point to itself( The internal DNS Server) and all future 2000 Servers should point to it as well.

Once the server is pointing to itself it will not poll over the ISDN.

To configure the Server for Internet access check out Q231794 and search the help files for DNS "Forwarders"

This is a very common mistake, as most people configure it in the same way NT 4 worked.

Hope this helps

Andy P

by nordeide

Andy P,

Thank you for your reply. I do appreciate the tip of not using the ISP's DNS under TCP/IP Properties, but unfortunately, it means that I have to work some more on the Internet access part...

-Rolf.

by danny.kapp

Use NAT(network address translation) on the gateway pointing to the external IP and have your DNS settings on the server and workstations point to your internal DNS and set your internal DNS server to point to your ISP as an forwarder for any name queries your DNS is unable to resolve. This should reduce the external name requests drastically.

by ilovenetworking

Hi,

The first DNS server you have should be the one of you Y2K server's. The second one should be your ISP's.
The windows time service may be causing the unwanted connections to the Internet. It's trying to synchronize with an external time source. Go to services, stop the service and change the startup option to manual.

Peace,

Witold S.

This discussion is closed to new replies.