• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

DNS Question

I don't pretend to be an expert in DNS ....

But I've got a dual-NIC server, one side pointing to the outside world, the other inside.  The default gateway points externally, as does the DNS.  If I do an NSLOOKUP on the box, I jump to the outside (142.77.1.1) UUNet outside address.  But if I type PING and put an internal DNS name in, it knows to use my internal DNS.

My question is how does it know to go external or internal, especially when my default gateway points outward.  So if I work for xyz.com, and type ping donald.inside.xyz.com it resolves the IP on my internal DNS, but if I type ping google.ca it resolves outside ... where is that decision made???

Thanks!
0
canadiense
Asked:
canadiense
1 Solution
 
CDCOPCommented:
If you have a forwarder setup, it will ask the server listed where the dns entry is. I'm not 100% sure how you have your system setup, so I can say for sure on your's, but that's the general idea. If you right click on the DNS server in the DNS snapin go to properties and in those tabs you will find the forwarder section.

Also, check this out:
http://www.petri.co.il/install_and_configure_windows_2003_dns_server.htm
0
 
NJComputerNetworksCommented:
dual nic

int Nic:  
IP:10.10.10.5
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS: 10.10.10.25

Ext Nic:
IP: 142.77.1.1
Subnet: 255.255.255.252
Gateway: 142.77.1.12
DNS: 154.45.25.19


All Windows 2000 and higher clients that participate in an Active Directory domain, must use the internal Windows DNS infrastructure for DNS resolution.  This is because Active Directory is DNS based.  In order for the client or server to "talk" to AD, it would be preferrable to do this using DNS.  Therefore, the internal Windows DNS is very important....and must be used.

When you create a domain, the domain name (i.e. company.local) is also created.  When a server or client joins the domain, the default behavior is to add the company.local DNS suffix automatically to the clients TCP/IP properties.  by doing this, the client will automatically append company.local to all requests to DNS.

so, if you look at your TCP/Ip properties...and click on the DNS tab, you should see company.local as one of the DNS suffixes.

The DNS suffixes are important as this is the domain the client will query for when looking for records.

For example,

if a client is looking for SERVER2....  The client will automatically append the DNS suffix company.local to the query to DNS.  So the query actually becomes SERVER2.company.local  This is done by defualt.  if you add another DNS suffix to the client, (i.e. yahoo.com), the query appends both...

server2.company.local
server2.yahoo.com

In a normal DNS heirarchy, the root internal DNS server will forward outside DNS lookups to ISP DNS servers.  In this way, if the internal DNS structure can not find a record, Internet DNS servers take over the search.

So, on the company.local DNS servers, they would forward requests if they can not be resolved internally.  When a search for www.experts-exachange.com is done, the internal DNS servers will relieze that this request is not for COMPANY.LOCAL domain...but rather for experts-exchange.com domain.  Therfore, they forward the request to the internet DNS servers to find record WWW.


0
 
canadienseAuthor Commented:
Man ... that was fast!

Thanks ...

CDCOP - I was looking more for how the local station determined the route.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now