Re: Appending to absolute name on failure

[Garth P. <ga...@tw...>]

Thank you!

On Fri, May 9, 2014 at 12:34 PM, Jack Tavares <j.t...@f5...> wrote:
> If you want the host name to be treated like an absolute name, you need
> to provide an absolute name.
>
> In other words, terminate your host name with a dot "."
>
> So your code should be:
>  Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.",
>
>> -----Original Message-----
>> From: Garth Patil [mailto:ga...@tw...]
>> Sent: Friday, May 09, 2014 11:56 AM
>> To: dns...@li...
>> Subject: Appending to absolute name on failure
>>
>> I am using the dnsjava library to query a NAPTR record:
>>
>>     SimpleResolver resolver = new SimpleResolver(X.X.X.X);
>>     resolver.setPort(53);
>>     Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net",
>> Type.NAPTR);
>>     lookup.setResolver(resolver);
>>     Record[] records = lookup.run();
>>
>> When the initial query fails for some reason (e.g. REFUSED), the library
>> seems to be adding additional terminating domains to the end of the
>> hostname string. E.g.
>> "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net"
>> becomes
>> "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.blah.com"
>> "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.foo.net"
>>
>> These are specified in my /etc/resolve.conf as
>>
>>     search blah.com foo.net
>>
>> Is there a way to tell the lookup that the initial name passed to the Lookup
>> constructor is absolute, and no additional resolution should be done?
>>
>> Thanks,
>> Garth
>>
>> ------------------------------------------------------------------------------
>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
>> &#149; 3 signs your SCM is hindering your productivity &#149; Requirements
>> for releasing software faster &#149; Expert tips and advice for migrating your
>> SCM now http://p.sf.net/sfu/perforce
>> _______________________________________________
>> dnsjava-users mailing list
>> dns...@li...
>> https://lists.sourceforge.net/lists/listinfo/dnsjava-users