Dlink router / DNS - Windows 2000 DNS problems

[Guest]

Hell
I am tring to do this w a dlink router 604 which has a public ip and private IP , Also I have Windows 2000 server setup as DNS ad integrated with ip 192.168.0.5 also it has a name server and WWW / Exchnage runing on i
This is my setu
WAN port= Public IP which what I have setup as my NS at the registrar company
So if you resolve to my domain name, your should to the Public IP

On the router LAN side I have 192.198.0.
My DNS / Exchange / Web server has 192.198.0.5 addres
Under Virtual server, I allowed SMTP port 25, DNS 53 and www port 80 which oint to my windows 2000 server

If I get a request for mail from outside. The router will give the private IP 192.198.0.5 as the holder for my MX record and it’s getting this from my internal DNS which is the same host 192.198.0.5

If you type nslookup and try to resolve to my domain name you will get my private IP 192.168.0.

If I take the router out and assign my public IP to the my DNS/Exchange/Web server, it works ok. So I think I am doing something wrong but it’s not obvious
Dlink wasn't able to hel
Thank

 

[Deji Akomolafe]

On the router's configuration, tell it to use your ISP's DNS server for
resolution, instead of using your LAN DNS server.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
MVP - Directory Services
www.readymaids.com - got SPAM problems?
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

Hello
I am tring to do this w a dlink router 604 which has a public ip and

private IP , Also I have Windows 2000 server setup as DNS ad integrated with
ip 192.168.0.5 also it has a name server and WWW / Exchnage runing on it

This is my setup
WAN port= Public IP which what I have setup as my NS at the registrar company.
So if you resolve to my domain name, your should to the Public IP.

On the router LAN side I have 192.198.0.1
My DNS / Exchange / Web server has 192.198.0.5 address
Under Virtual server, I allowed SMTP port 25, DNS 53 and www port 80 which oint to my windows 2000 server


If I get a request for mail from outside. The router will give the private

IP 192.198.0.5 as the holder for my MX record and it's getting this from my
internal DNS which is the same host 192.198.0.5.

If you type nslookup and try to resolve to my domain name you will get my private IP 192.168.0.5

If I take the router out and assign my public IP to the my

DNS/Exchange/Web server, it works ok. So I think I am doing something wrong
but it's not obvious

 

[Kevin D. Goodknecht [MVP]]

In

Hello
I am tring to do this w a dlink router 604 which has a public ip and
private IP , Also I have Windows 2000 server setup as DNS ad
integrated with ip 192.168.0.5 also it has a name server and WWW /
Exchnage runing on it
This is my setup
WAN port= Public IP which what I have setup as my NS at the registrar
company.
So if you resolve to my domain name, your should to the Public IP.

On the router LAN side I have 192.198.0.1
My DNS / Exchange / Web server has 192.198.0.5 address
Under Virtual server, I allowed SMTP port 25, DNS 53 and www port 80
which oint to my windows 2000 server


If I get a request for mail from outside. The router will give the
private IP 192.198.0.5 as the holder for my MX record and it's
getting this from my internal DNS which is the same host 192.198.0.5.

1.Are you using your local AD DNS server to host your public DNS zone?
2.Is your AD domain name the same as your public domain name?
Neither of these is recommended, especially question 1. Move DNS to another
machine for the public zone, or better yet, host your public DNS elsewhere,
such as with your registrar.

If you type nslookup and try to resolve to my domain name you will
get my private IP 192.168.0.5

This is the proper behavior for an Active Directory Domain, this is so
domain members can find the Sysvol DFS share and get their Group Policy
objects at \\dnsdomainname\SYSVOL\dnsdomainname\policies

If I take the router out and assign my public IP to the my
DNS/Exchange/Web server, it works ok. So I think I am doing something
wrong but it's not obvious

You need two DNS servers so you can set up a split namespace. One public for
external clients and one private for internal clients. Don't do this in one
DNS server.