General discussion

Locked

DNS server and active directory

By promartinus ·
I have one question concerning DNS server configurations could someone who knows exact
"how it works" enlighten me with my doubts ?
here it is:

my server is connected trough Linksys NAT router/firewall router acts as a DHCP server.

my WAN IP is separated (different class, different network eg. 67.23.21.54 ) form my LAN IP's (192.168.1.1)

my linksys router automatically obtains DNS IP's of my ISP and maps them, so my local network uses Linksys router IP adress as DNS...

I am forwarding the port of DNS service, to the win2003 server machine (mainserver), running DNS server software.

and I am forwarding FTP service port to other machine with win NT4.0(ftpserver) running FTP server.

Both machines are in the same Active Directory Domain, (mydomain.local) where (mainserver) is the primary domain controller and (ftpserver) is standalone server pre win 2000 defined.

My external domain is dexternal.com

Users connecting trought the internet to:

ftp.dexternal.com are forwarded to the (ftpserver)
(becouse of ftp service port is forwarded by the router)

Question is:

When users type ftpserver.dexternal.com

the (mainserver) on dexternal.com running dns should pass ftp server IP to the user...

that what the theory is..

I want to know this: once internet user, WAN tries to access LAN computer, that should be routed in order to work..

Straight question is:

Does DNS server do the routing, of WAN to LAN while static DNS entry points to LAN ip ??

How DNS is related to the routing options.. can still use it with linksys ?

Do I need to use WIN 2003 routing features, in order to have whole dns functionality?

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by curlergirl In reply to DNS server and active dir ...

I think you are getting confused between the internal LAN users and the external WAN users as far as DNS is concerned. First of all, your internal DNS server on the Win2K3 box should be configured to forward DNS requests to your ISP's DNS servers, and your internal LAN users should be configured to use only the internal Win2K3 DNS server (not the Linksys router). The Linksys router should also be configured to use your Win2K3 server as DNS server.

Second, forwarding a port to your internal DNS server from your router does nothing unless your internal DNS server is publishing itself on the Internet, which requires it to have its own public IP address. So, unless you have set your Linksys router to forward a specific IP address to your Win2K3 server for DNS purposes, and unless you have published, via your domain name registration, that your Win2K3's public IP address is the authoritative DNS server for your domain, forwarding the packets isn't doing anything at all, because your external users are not looking to your Win2K3 server for DNS services.

You need to get firmly in your mind that routing and DNS are two completely different things. Routing has to do with moving IP packets from one network to another based on IP addresses, subnetting and gateway connections. DNS has to do with resolving IP addresses to host names. DNS happens first before routing. As an example:

Host A sends out a request for connection to ftpserver.dexternal.com. This request goes to Host A's DNS server, which resolves the name ftpserver.dexternal.com to 67.23.21.54, and sends this information back to Host A. Host A then sends a request to its gateway (router) for a connection to 67.23.21.54. The router routes the packet to the appropriate next hop (which would be its external gateway), which then routes it along to the next appropriate hop, etc., until it finds the router with that specific IP address, which then routes the packet to your ftp server.

Hope this helps!

Back to Windows Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums