I should have mentioned that before - It's a long story, but the 169.254.X.Y. is by design. Yes, it also happens to match the APIPA addressing, but that can't be helped and so the address are indeed coming from the DHCP server and that part is working as expected.
-----Original Message----- From: Mike Semon [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 10:06 PM To: NT System Admin Issues Subject: RE: NSLookup - results are not as expected That's not good. The 169.x.x.x address is coming from a Windows service called APIPA (Automatic Private IP-addressing). APIPA is a service to dynamically assign IP addresses to network clients when they can't reach the DHCP server. Mike -----Original Message----- From: Bryan Garmon [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 8:38 PM To: NT System Admin Issues Subject: NSLookup - results are not as expected I'm losing hair on my head trying to understand what determines the order of the IP addresses when they are listed in NSLookup? For example when I run nslookup against my AD Domain name, I receive the result: Name: name.domain.com Addresses: 169.254.0.152, 169.254.0.150, 169.254.0.151 What I am expecting to see is this: Name: name.domain.com Addresses: 169.254.0.150, 169.254.0.151, 169.254.0.152 How can the order be changed? ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
