Advertisement

04.08.2007 at 08:54AM PDT, ID: 22498601
[x]
Attachment Details

PING resolves wrong IP address, DNS Cache entry is wrong on a multi-homed domain controller

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.6
Tags:

wrong, ip, dns, address, ping

Hello,

I am having difficulty trying to get my head around something with regards to name resolution and PING.

In particular, I have an incorrect entry in the DNS Cache on the machine in question and ping seems to resolve the name to the wrong IP. This name resolution problem is causing some headaches on the domain.

I have I Series AS/400 with integrated Windows Server card. Windows 2003 R2 SP1 is installed and is a DC and holds the FSMO roles. There are 3 other DCs on the network although this is the PDC. For those not familiar with this setup, these boxes have an internal token ring network that allows OS/400 and Windows to communicate directly. The network topology of the box is as follows:

   I5 AS/400 Box:
_____________________________________
|    OS/400                                  Windows        |
|                                                                         |
|     Int. NIC                                      Int.NIC         |
|   192.168.3.11------><----------192.168.3.12   |
|   host: I5                                   Host I5Win      |
|                                                                        |
|     Ext NIC                                    Ext NIC         |
|    192.168.1.12                        192.168.1.11  |
|          |                                               |             |
|         V                                             V             |
          -----------------Lan-------------------

Just for note, the external NICs are paired Gigabit adapters (INTEL Pro1000) if that makes any difference

The windows NIC DNS server entry is pointed to itself (192.168.1.11) and everything works as expected if you try to resolve any names using the FQDN. "Append Suffix" is set and is set to the local domain.

However for some reason, if you dump the DNS Cache you get:

   i5win
   ----------------------------------------
   Record Name . . . . . : I5WIN
   Record Type . . . . . : 1
   Time To Live  . . . . : 573152
   Data Length . . . . . : 4
   Section . . . . . . . : Answer
   A (Host) Record . . . : 192.168.3.11


   Record Name . . . . . : I5WIN
   Record Type . . . . . : 1
   Time To Live  . . . . : 573152
   Data Length . . . . . : 4
   Section . . . . . . . : Answer
   A (Host) Record . . . : 192.168.1.11

   qi5
   ----------------------------------------
   Record Name . . . . . : QI5
   Record Type . . . . . : 1
   Time To Live  . . . . : 573152
   Data Length . . . . . : 4
   Section . . . . . . . : Answer
   A (Host) Record . . . : 192.168.3.11

It's not that I wouldn't expect two entries, and in fact, I need to clean up the DNS records on a reboot as typically the 3.12 address registers itself even though I have set *not* to. But why and how is 3.11 getting into this local machines cache as I5Win?

This is driving me insane. Is there any way to remove this entry from the cache? flushing has no effect. Using NSLookup retrieves the correct results.
Answered By: Computer101
Expert Since: 04/07/2001
Accepted Solutions: 39510
Computer Expertise: Advanced
Computer101 has been an Expert for 7 years 9 months, during which he has posted 147805 comments and answered 39510 questions. Computer101 is just one of 137 experts in the AS / 400 Zone. 3 experts collaborated on this answer, which was graded an "A" by the asker.
 
 
20081119-EE-VQP-48