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

Domain DNS Problem

I am running Windows Server 2003 and I have a secondary DNS called example.com.  I have a few records; www, ftp, etc... that I need to resolve internally for this domain and that is working fine.  However, my problem is that when I ping just example.com it does not resolve to anything.  Is there a way I can configure this DNS zone to resolve this to an address?  

Thanks,
Bob
0
NMLLC
Asked:
NMLLC
  • 2
  • 2
1 Solution
 
Erik BjersPrincipal Systems AdministratorCommented:
You need to make sure the name server records are correct for your domain.  Once the name server records are correct pinging example.com should ping the DNS or DC

eb
0
 
KvChaosCommented:
When you add www, ftp, etc.. you go to example.com and add host right?
For example.com itself, add a host with nothing specified (which means you left the field where you key in things like www, ftp, etc.. empty), and key in just the IP address. That should work.
0
 
NMLLCAuthor Commented:
eb,

Thanks for the reply, however I'm still a little confused.  There are 2 NS records in the secondary zone pointing to my local dns zone servers.  Maybe I should explain further.  I have a local DNS zone called example.local serving my internal DNS.  I have a secondary zone called example.com which have a few A Host records.  If I ping example.local it resolves to my DNS server which is what I would expect.  What I would like is for example.com to resolve to an external ip address or our web hosting domain.  I hope this helps explain my situation.
0
 
KvChaosCommented:
Like what I have said. Go to your forward lookup zone, go to example.com, add an A Host record.
Your first field: Name (uses parent domain name if blank):
Like that it says, just leave it blank. The IP you specified here will resolve http://example.com.
0
 
NMLLCAuthor Commented:
KvChaos,
Never thought of that and it works perfectlyl!  Thanks for the solution.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

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