Re: Hot! Server 2003 multiple IP binding order?
From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 03/30/04
- Next message: COTSWOLD: "AD-INTEGRATED DNS"
- Previous message: Roger Abell: "Re: DNS Server design"
- In reply to: IPHound: "Hot! Server 2003 multiple IP binding order?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Mar 2004 23:49:22 -0700
First, you mention the "correct IP" whereas technically
they are all correct. Correct is your perspective, about
which the resolution methods are ignorant.
Second, your said ping, but did not say pinging with what
name. Did you cause a DNS or a WINS resolution ??
Wins will know the "correct" IP, as that is where you say
you have NetBT bound (and so I assume you meant the other
interfaces which have all the rest of the IPs do not have NetBT
bound to it/them).
Third, once your test machine gets an IP for the machine, it will
stick with it since it just recycles this info from the cache. To
validly test you need to flush the resolver cache between each
attempt (ipconfig /flushdns)
The final comment that has some bearing here is that for the
DNS resolution you should (unless the AD DNS you say is
being used has been adjusted from install settings) see the IP
returned from DNS cycling through all IPs (keep in mind that
this pseudo-round-robin is not per querying client, just per
query - - - so, if you do not see perfect cycling it is because
some other client did a query on the name).
Now, you stated what you were seeing and asked if it was
normal. Hopefully the above points will help refine what
you are asking as it sort of mixed apples and oranges regarding
NetBT vs DNS. You then ended the post with a "please help"
Was that just a please help with understanding what is happening?
Or is this causing some sort of difficulty for you ??
-- Roger Abell Microsoft MVP (Windows Server System: Security) MCSE (W2k3,W2k,Nt4) MCDBA "IPHound" <anonymous@discussions.microsoft.com> wrote in message news:153cc01c415f4$1eac7a40$a301280a@phx.gbl... > I have a server 2k3 running in an NT domain (with WINS > resolution), but pointed to an adjoining AD DNS server > (with AD integrated zones). > > I am attempting to run multiple ip addresses, which > appear to work fine, but when I ping itself the box > consistently ignores the primary IP address x.x.x.99 and > instead chooses the lowest ip on the card. (ping myserver > yeilds x.x.x.91). > > If I delete x.x.x.91, the next lowest ip address is used. > however, nbtstat is always registered using the primary > x.x.x.99 address. > > Is this normal, or is there some way (other than the > hosts file) for the computer to "know itself" using the > correct ip? I have thought about creating an extra "non- > integrated" zone on the AD servers, but I'm not sure what > the effect of this will be. > > Please help!
- Next message: COTSWOLD: "AD-INTEGRATED DNS"
- Previous message: Roger Abell: "Re: DNS Server design"
- In reply to: IPHound: "Hot! Server 2003 multiple IP binding order?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
