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

Problems with Windows 2000 server DNS

We are trying to implement internal DNS to resolve our website names to the internal address instead of the external address when we are in the office.  The DNS was set up on the server and nslookup returns the correct responses, but when simply pinging the site, it times out and can't find the host.

also of note:

> set query=any
> malachite
Server:  UnKnown
Address:  192.168.1.15  <<<<<<<Our DNS Server

malachite       internet address = 10.0.2.122   <<<<<<<<<  Correct mapping
malachite       nameserver = emerald
malachite
        primary name server = emerald
        responsible mail addr = admin
        serial  = 2
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)
emerald internet address = 192.168.1.15
emerald internet address = 192.168.0.15


NSLOOKUP works fine.  But right after that....


C:\Documents and Settings\XXXXXXX>ping malachite
Ping request could not find host malachite. Please check the name and try again.
0
rivetgeek
Asked:
rivetgeek
  • 6
  • 4
1 Solution
 
fetch_Commented:
Are you using WINS also?  If so, make sure WINS has the right mapping.  You may also need to do

ipconfig /flushdns

on that pinging machine to make it query the DNS server again.
0
 
rivetgeekAuthor Commented:
One more thing to note, I ran wireshark and saw only NBNS packets going out. Shouldn't there be a DNS query going out to port 53 of the nameserver?
0
 
rivetgeekAuthor Commented:
We are not using WINS.  I have tried to flush dns with no better results
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
rivetgeekAuthor Commented:
To clarify,

When i set my dns server to our internal dns server, I see DNS query packey packets when doing nslookup, but not when trying to browse or ping to that name (example: malachite).  When trying to ping, I see NBNS packets if netbios over tcp/ip is configured.  If it's not configured, no packets are going out at all.
0
 
fetch_Commented:
can you see the host record when you look in the DNS snap-in?  Is the pinging machine using the DNS server that you saw had the correct host record?  (Could be DNS replication issue, if not).  I'm not sure what to tell you about the NBNS packets.  
0
 
fetch_Commented:
this article: http://en.wikipedia.org/wiki/NBNS#Name_service makes me think the computer is looking for a WINS server when it sends out NBNS packets.  Can you do ipconfig /all and double check that there's no WINS server addressed.  Please post the results.
0
 
rivetgeekAuthor Commented:
Ok so it looks like the problem is that I had some records configured that werent fully qualified.  

So if I have a zone of ABC.com, and a host of malachite,   i would have to ping it with malachite.narratus.com, correct?

Is there a way to use non FQDNs?
0
 
rivetgeekAuthor Commented:
er woops ping it with malachite.ABC.com i meant
0
 
fetch_Commented:
I'm not sure i follow your question.  Can you restate it and post the results of the ipconfig /all?
0
 
rivetgeekAuthor Commented:
The problem is not with the client.  

It was a bad zone definition.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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