× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Kirk,

I'm not sure that this is governed by a standard, since it's not part of the way things work under-the-covers, it's just a feature of a program.

But, I agree with your client. If you do ping 'bob', it should be looking for 'bob' first, then 'bob.xxxxx.yyyyyy.com', unless 'yyyyyy.com' is in your DNS search list.

You can add a . as a suffix if you don't want it to automatically append the domain name. So you could do 'bob.xxxxx.yyyyyy.com.' (note the trailing dot) and it should ONLY look for that exact name. Likewise, you could do 'bob.' and it'd only look for bob without any domain suffix.

Does that help?

-SK


On 7/16/2014 4:56 PM, Kirk Goins wrote:
How the iSeries at 7.1 does it.
CFGTCP Option #12
Host Name = HHHHH
Domain name = xxxxx.yyyyyy.com
Domain search list = *DFT

Do ping to some name like just plain old BOB
The iSeries searches for BOB.XXXXX.YYYYYY.COM
If not found the iSeries searches for BOB.YYYYYY.COM
Per my client that 2nd search should not happen
Per IBM that is compliant with DNS standards
In this case it was causing issues and invalid address was being returned.

Da question fo any DNS GURU's Can you point me to and RFC or ??
That outlines the correct search method that a computer should do
per standards. I want to provide docs that prove that he DNS search
function
on the iSeries is working or not working correctly.

Thanks



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.