Forum Moderators: phranque

Message Too Old, No Replies

Problem with Microsoft DNS-server

ms Dns

         

sunda

8:42 pm on Aug 31, 2003 (gmt 0)

10+ Year Member



Hello,

I have recently bought me a Router (Netgear).
Since that day I got myself a little problem (don't know if the router is to blame, or if it's just bad luck).

I have mydomain.com and using Microsoft Server 2000 as OS for the server.
I also have IIS as webserver.
My external IP is connected to my Router.
I have an internal static IP for the server. A DMZ is created on the Router, with the ip of the server as host.
I also have two client computers connected to the router, they are using DHCP.
On my server I have added the DNS-host of www (external ip) and www (internal ip).
My problem is this...
When I connect to the site from one of my client computers, it was taking me ALOT of time to access them when I hade only the external ip as DNS-host. But it was working 100% for visitors from outer space :-)
I then added the internal IP too as a DNS-host of www. Now it works better for my clients.... sometimes..

My opinion of this is that it seems like the DNS sometimes is giving me the internal IP as host, but sometimes the external (I have this problem with the clients when they try to access the external ip).
Anybody knows of a way to decide WHICH of the DNS-records to be used under what surcomstances? I would like every 192.168.x.x IP to use the internal DNS-record, while everyone else should use the EXternal.

Thank you for any kind of help :)

Regards,
Johan

dmorison

8:48 pm on Aug 31, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi Johan,

I run a similar setup, and don't bother with DNS for the internal address. The only DNS address record is for the external IP, i.e.

www.example.com --> IP address assigned to my cable modem

For my internal machines, I override DNS with an entry in each machines local HOSTS file, so

www.example.com --> 192.168.1.x

sunda

9:04 pm on Aug 31, 2003 (gmt 0)

10+ Year Member



Ah, okey.
Yeah, that is one way to do it.
But it should be able to do a more reliable solution. The clients shouldn't have to be involved. There must be a way to deal with this on the server..
Don't you agree?
Anyone knows?