RE: NSLookup - results are not as expected
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 ~
RE: NSLookup - results are not as expected
Thanks to everyone who for confirming that the results can be returned in any order, and that it shouldn't matter. I'll start troubleshooting a different route and post with a new subject line. -Original Message- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 1:27 AM To: NT System Admin Issues Subject: Re: NSLookup - results are not as expected On Thu, Feb 21, 2008 at 9:38 PM, Bryan Garmon [EMAIL PROTECTED] wrote: I'm losing hair on my head trying to understand what determines the order of the IP addresses when they are listed in NSLookup? The DNS specification says that if multiple RRs (Resource Records) exist for a given domain name, they may be returned in any order. How can the order be changed? Short answer: It cannot. -- Ben ~ 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 ~
RE: NSLookup - results are not as expected
Well, I keep getting the error message semaphore timeout expired or Name no longer available on any machine that tries to join the domain. This was the only thing I could find that appeared to be out of whack based on my limited DNS knowledge. -Original Message- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 10:14 PM To: NT System Admin Issues Subject: RE: NSLookup - results are not as expected scratches head Why does it matter? Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -Original Message- From: Bryan Garmon [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 9: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 ~
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 ~
RE: NSLookup - results are not as expected
scratches head Why does it matter? Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -Original Message- From: Bryan Garmon [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 9: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 ~
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 ~
Re: NSLookup - results are not as expected
I think it's more likely he sanitized the output ;) Mike Semon wrote: That's not good. The 169.x.x.x address is coming from a Windows service called APIPA (Automatic Private IP-addressing). -- Phil Brutsche [EMAIL PROTECTED] ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~ ~ http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm ~
Re: NSLookup - results are not as expected
When you have multiple A resource records for a particular DNS name some DNS servers return the results in a random order. Microsoft's DNS service isn't one that randomizes the lookup results. This is something you typically see when the name server (or the caching name server) the client is pointing to is BIND on Linux/*BSD/some commercial UNIX. In the grand scheme of things it really doesn't make a difference. Bryan Garmon wrote: 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? -- Phil Brutsche [EMAIL PROTECTED] ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~ ~ http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm ~
Re: NSLookup - results are not as expected
From memory lookups can appear in any order. I'm sure ive done lookups to the same domain and have a varying order of result. It shouldnt make any difference though. Greg 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 ~
Re: NSLookup - results are not as expected
On Thu, Feb 21, 2008 at 9:38 PM, Bryan Garmon [EMAIL PROTECTED] wrote: I'm losing hair on my head trying to understand what determines the order of the IP addresses when they are listed in NSLookup? The DNS specification says that if multiple RRs (Resource Records) exist for a given domain name, they may be returned in any order. How can the order be changed? Short answer: It cannot. -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~ ~ http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm ~
