John, Have you got a reverse zone on your DNS servers? And are the actual DNS servers themselves correctly registered in this zone ( with their IP address being mapped to their FQDN)? Kind regards, Jeremy Jeremy Saunders Senior Systems Engineer ”ITS - passionate about winning” IBM Logicalis (Integrated Technology Services) Level 2, 1060 Hay Street West Perth, WA 6005, AUSTRALIA Visit us at http://www.ibm.com/services/au/its Phone: 132 426 Fax: ; 08 9261 8536 Mobile: TBA E-mail: jeremy.saunders@xxxxxxxxxxx "John Hardwick" <jhardwick@xxxxxx et> To Sent by: <thin@xxxxxxxxxxxxx> thin-bounce@freel cc ists.org Subject [THIN] Re: OT: 2k3 NSLookup / DNS 04/11/2004 04:03 Weirdness AM Please respond to thin Neil, I've checked both of the DNS servers and they don't show a root server (.) zone under forward lookup zones (I assume that is where it would be.) The servers are set with forwarders right now but they are just set to forward to my outside DNS servers. "Do Not use recursion for this domain" isn't checked. There are no suffixes defined on client side and it is set to append primary and connection specific DNS suffixes and append parent suffixes of the primary DNS suffix. From IPConfig. Primary Dns Suffix . . . . . . . : KC.nXio.net DNS Suffix Search List. . . . . . : KC.nXio.net nXio.net If I point NSlookup to my DCs it has the problem.. if I point NSlookup to any outside name server it doesn't. MS says that NSlookup knows if the DNS server I am connecting to is inside the domain or not and that's what it uses to determine if it appends or not. I don't agree with that. I guess my frustration is that MS's stance is that "sometimes" Nslookup performs like this and that it doesn't mean anything... thus they won't even acknowledge that it could be coming from whatever the original problem is. If anyone does an nslookup while a member of a 2k3 or 2000 domain for an outside host without appending a period to it will always resolve the first time correct? John Hardwick President nXio, LLC. 913-754-8120 x125 www.nxio.net -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Braebaum, Neil Sent: Wednesday, November 03, 2004 12:00 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: OT: 2k3 NSLookup / DNS Weirdness Do your DNS servers thing they are root servers? (is there a . zone?) When you fully qualify a name it looks like you are getting a response, so I would think it's either down to suffixes and search lists (client-side), or possibly recursive settings at the server end (possibly coupled with maybe thinking it's a root server?). Neil > -----Original Message----- > From: thin-bounce@xxxxxxxxxxxxx > [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of John Hardwick > Sent: 03 November 2004 17:55 > To: thin@xxxxxxxxxxxxx > Subject: [THIN] OT: 2k3 NSLookup / DNS Weirdness > > All, > > I've been working with MS on this and they can't give me an > answer either. > > From a 2K3 member server or even on the DCs themselves if I > do a nslookup for the short name of a server... i.e. Server1 I > receive an instant response. > > If I do a lookup for the full name i.e. > Server1.domainname.tld I get a response timed out followed by > a response. > > If I do a lookup for Server1.domainname.tld. (note the period > at the end) I get an instant response with no failure. > > All of the 2K3 Servers are pointed to the 2K3 DCs for DNS > resolution and I've tried having the 2K3 DNS servers forward > and not forward with no difference in the results. MS's > statement is that NSLookup has different logic and behaves > differently than a ping etc and that it knows when it should > append the local domain suffix or not. All of the machines > have no suffixes defined for them. What made me notice this > was periodic failures on my anti-spam stuff where it would > lookup for example mail.citrix.com.2k3domainame.tld > > I know from other 2K3 deployments I've done that out of the > box I should be able to do a nslookup without having to put a > period at the end of the query or having to change the suffix > in NSlookup. *********************************************** This e-mail and its attachments are confidential and are intended for the above named recipient only. If this has come to you in error, please notify the sender immediately and delete this e-mail from your system. You must take no action based on this, nor must you copy or disclose it or any part of its contents to any person or organisation. Statements and opinions contained in this email may not necessarily represent those of Littlewoods. Please note that e-mail communications may be monitored. The registered office of Littlewoods Limited and its subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB. Registered number of Littlewoods Limited is 262152. ************************************************ ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm N�Y礱*h��+g����:yb���p�� ����zw&���ƭN� +r�M8N���'��g����:r���r薈2 ��z��q�m�����)Šܜ�e,y��N� X��Ш����x�y,j�����i�^j�m��������)�������b��-�I칻�&�J��r��z��z���-��Zq�b�y�u�z�^m�h�X��m���)�z�܊���X����