Hi all, Not sure if anyone else has experience this, however we noticed this once the default NSINTERADDR got corrupt.
Our impression was that if a hostname could not be resolved using the first name server, the next name server on the NSINTERADDR list will be searched. This is not the case. We noticed this as the hostname could resolve from the MS command prompt showed the : D:\temp>nslookup wks8546m Server: server03.xxx.yyy.zzz Address: 100.18.15.7 Name: myhost.xxx.yyy.zzz Address: 100.181.195.11 EZB3170I Server: server01.xxx.yyy.zzz EZB3172I Address: 100.18.14.7 EZB3010I *** server01.xxx.yyy.zzz can't find myhost: Non-existent domain *** We do have 100.18.15.7 listed in our TCPDATA: NSINTERADDR 100.18.14.7 NSINTERADDR 100.18.14.8 NSINTERADDR 100.18.14.9 NSINTERADDR 100.18.15.6 NSINTERADDR 100.18.15.7 NSINTERADDR 100.18.2.5 NSINTERADDR 100.16.18.8 If I move NSINTERADDR 100.18.15.7 up the list (namely first/default), the issue is resolved. Surely this isn't how it should work and defeats the purpose of having a list. How do I get it to search the rest of the listed NSINTERADDR ? Thanks in advance for any assistance received. Kind Regards, Vikesh Bhoola Please Note: This email and its contents are subject to our email legal notice which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
