dnsjava-users — The dnsjava mailing list

Q: Adding MX Records

[Edwin R. R. <er...@mo...>]

Hello all,
 
Disclaimer: I'm relatively new to the Java platform, so, please forgive
me if I am making any obvious rookie mistakes.  
 
Summary: I am working with dnsjava to write some classes to replace our
DDNS PERL libraries (NET::DNS).  I can successfully connect to my
nameservers, run queries, extract zone transfers, and even add "A
Records", however, I am having trouble adding an MX record to a zone.  
 
1)  Here is a snippet of the code I am using to add an A record (that
works):
 
                Name Nzone         = Name.fromString(zone);
                Name Nhost         = Name.fromString(host, Nzone);
 
                Update update      = new Update(Nzone);
                //System.out.println("Update: " + Nhost + " " +
typeValue + " " + ttl + " " + ip);
                
                Record r = Record.newRecord(Nhost, typeValue, dclass); 
 
                update.add(Nhost, typeValue, ttl, ip);
                
                Resolver res       = new SimpleResolver(this.master);
                                     res.setTSIGKey(this.keyName,
this.keyValue);
                                     res.setTCP(true);
                     
                Message msg = res.send(update);
                
                if (doesRecordExist(r, res))
                    return true;                          
 
2)  Here is the snippet of code based on the above that tried to adapt
to add MX records (does not work yet):
 
                Name Nzone         = Name.fromString(zone);
                Name Nhost         =
Name.fromString(Nfqdn.getLabelString(0), Nzone);
 
                MXRecord m         = new MXRecord(Nfqdn, dclass, ttl,
pref, Ntarget);
                
                System.out.println("m: " + m.toString());
                
                Update update      = new Update(Nzone);
                //System.out.println("Update: " + Nhost + " " +
typeValue + " " + ttl + " " + ip);
                
                Record r = (Record) m; 
                
                System.out.println("r: " + r.toString());
 
                update.add(r);  //I've tried both update.add(r) and
update.add(m)
                
                Resolver res       = new SimpleResolver(this.master);
                                     res.setTSIGKey(this.keyName,
this.keyValue);
                                     res.setTCP(true);
                     
                Message msg = res.send(update);
                
                if (doesRecordExist(r, res))
                    return true;                            
 
 
 
3)  When i call the toString() method of my MX record objects, they do
appear to be correct:
 
m: wwwwww.zzogy.com.    3600    ANY     MX      10 mail.yahooo.com.
r:   wwwwww.zzogy.com.    3600    ANY     MX      10 mail.yahooo.com.

(these are just tests)
 
 
Thanks in advance for any assistance/pointers you can offer.
 
I have programmed mostly PERL for the last 10 years or so, but I am
really liking Java.  It's much cleaner and organized.
 
-Edwin
 
 

dnsjava 1.4.0 released

[Brian W. <bwe...@xb...>]

After far too long, 1.4.0 was just released.  I don't think I ever sent an 
official notice of 1.3.3, since I expected there to be another version 
coming soon, but it ended up taking a few months.

The most noticable change is that DNS types and classes were previously 
stored in shorts; they are now stored in ints.  This may cause small
compatibility problems.

Full changelog below, including the 1.3.3 changes.

Brian

-------------------------------------

8/21/2003
	- 1.4.0 released.

8/20/2003
	- Add the ReverseMap class, which contains functions to construct
	  names to be used in reverse map zones.

8/13/2003
	- When looking up a one label unqualified name which fails to match
	  all searchlist entries, don't append the root label and try again.
	  This is recommended by RFC 1536, section 6: "Only if the name, so
	  generated, returns an NXDOMAIN is the original name tried as a Fully
	  Qualified Domain Name. And only if it contains at least one period."

7/18/2003
	- Remove lots of unused imports. (Jared Richardson <ja...@nc...>)

7/14/2003
	- Fix a long-existing bug where empty records (in update messages)
	  were incorrectly handled
	  (reported by Kevin C Miller <ke...@an...>

6/22/2003
	- DNS types and classes are now represented as ints, not shorts.
	  This is an API change, but allows the full type/class range
	  to be used.

6/18/2003
	- Quoted strings didn't handle \ddd escapes.

6/17/2003
	- Fix an ArrayIndexOutofBoundsException triggered by load balancing
	  in the ExtendedResolver.
	  (reported by Norbert Desautels <nde...@gd...>)

6/1/2003
	- Add the Name.relativize() method to convert an absolute name to
	  a name relative to a specified origin.
	- Add the Update class, which contains helper routines used to
	  construct dynamic update messages.

5/28/2003
	- Replace org.xbill.DNS.utils.MyStringTokenizer with
	  org.xbill.DNS.Tokenizer, which is a far more robust and correct
	  DNS tokenizer.  Convert everything to use it.
	- Fix text format of TXT, NAPTR, and HINFO records.

5/28/2003
	- When constructing a record, check that all names are absolute.

5/27/2003
	- 1.3.3 released.

4/26/2003
	- The master file parser should accept BIND format TTLs.

4/10/2003
	- The Inet6Address class incorrectly parsed some addresses.
	  (reported by steve weiland <st...@wi...>)

4/7/2003
	- Records were not sorted properly (reported by
	  Joseph K Shraibman <jk...@ak...>)

4/2/2003
	- Fix off-by-one error in Name.compareTo (David Blacka)

3/30/2003
	- Add the ZoneTransferIn class, which performs incoming AXFR/IXFR
	- Make TSIG verification of multiple-message responses reentrant.
	- Fix incorrect string quoting.
	- Make records print on a single line by default; add the 'multiline'
	  option to use the more verbose format.

3/17/2003
	- Make the routine that converts an IP address from a string
	  more efficient and correct.
	  (based on a patch by Sean O'Neil <Se...@te...>)

2/12/2003
	- Fix an infinite loop that could occur when processing a response
	  containing a CNAME loop and an rcode of NOERROR.
	  (reported by Sean O'Neil <Se...@te...>)

1/25/2003
	- Cleanup and improvements to the ExtendedResolver class.

1/23/2003
	- Add the setMaxCache() method to the Cache class.
	- Check for non-absolute names when creating Records.

Re: Failing to query for Type.NS

[Brian W. <bwe...@xb...>]

On Fri, 23 May 2003, Jürgen Hoffmann wrote:

> I am trying to query a nameserver for a zone which should be configured
> their and the corresponding configured Nameservers.
> 
> Easily speaking I am trying to see if the nameservers for a given zone
> are configured correctly.
> 
> What I have so far is this:
> 
> Records [] r = dns.getAnyRecords("byteaction.de", Type.NS)
> for(int i=0; i<r.length; i++)
> {
> 	System.out.println(r[i].rdataToString());
> }
> 
> But this does not work. I hav tried to set the Resolver explicitly with
> 
> ExtendedResolver er = new ExtendedResolver(new String[]
> {"212.223.69.193"});
> dns.setResolver(er);
> 
> And then run the query but both won't work =(

You're issuing a recursive query for type NS, which is causing the server 
to recursively attempt to find the NS records in the child zone, not the 
parent zone.  Depending on the server configuration, this might not work.

Issuing a non-recursive query is not particularly difficult (turn off the 
RD flag in the DNS header of the query), but neither the dns or Lookup 
class allows you to do that (since it's not something that applications 
usually do),  You'd need to construct the message by hand and use the 
Resolver to send it.

Brian

Failing to query for Type.NS

[<jh...@by...>]

Hi All,

I am trying to query a nameserver for a zone which should be configured
their and the corresponding configured Nameservers.

Easily speaking I am trying to see if the nameservers for a given zone
are configured correctly.

What I have so far is this:

Records [] r =3D dns.getAnyRecords("byteaction.de", Type.NS)
for(int i=3D0; i<r.length; i++)
{
	System.out.println(r[i].rdataToString());
}

But this does not work. I hav tried to set the Resolver explicitly with

ExtendedResolver er =3D new ExtendedResolver(new String[]
{"212.223.69.193"});
dns.setResolver(er);

And then run the query but both won't work =3D(

Kind regards
=20
J=FCrgen Hoffmann

ByteAction GmbH
Auf der Beune 83-85
64839 M=FCnster
HRB33271

mobil:     +49 (0)163 29 83 002
phone:     +49 (0)6071 9612-0 (09:00-18:00 Uhr)
           0700 byteaction / 0700 29832284 (24x7)
fax:       +49 (0)6071 9612-20
           0700 29832284
Email:     jh...@by...
Internet:  www.byteaction.de

------------------------------------------------------------------------
--
This communication is intended only for the party to whom
it is addressed, and may contain information which is privileged
or confidential. Any other delivery, distribution, copying or
disclosure is strictly prohibited and is not a waiver of privilege
or confidentiality. If you have received this telecommunication in
error, please notify the sender immediately by return electronic
mail and destroy the message.
------------------------------------------------------------------------
--
=20
=20

Failing to query for Type.NS

[<jh...@by...>]

Hi All,

I am trying to query a nameserver for a zone which should be configured
their and the corresponding configured Nameservers.

Easily speaking I am trying to see if the nameservers for a given zone
are configured correctly.

What I have so far is this:

Records [] r =3D dns.getAnyRecords("byteaction.de", Type.NS)
for(int i=3D0; i<r.length; i++)
{
	System.out.println(r[i].rdataToString());
}

But this does not work. I hav tried to set the Resolver explicitly with

ExtendedResolver er =3D new ExtendedResolver(new String[]
{"212.223.69.193"});
dns.setResolver(er);

And then run the query but both won't work =3D(

Kind regards
=20
J=FCrgen Hoffmann

ByteAction GmbH
Auf der Beune 83-85
64839 M=FCnster
HRB33271

mobil:     +49 (0)163 29 83 002
phone:     +49 (0)6071 9612-0 (09:00-18:00 Uhr)
           0700 byteaction / 0700 29832284 (24x7)
fax:       +49 (0)6071 9612-20
           0700 29832284
Email:     jh...@by...
Internet:  www.byteaction.de

------------------------------------------------------------------------
--
This communication is intended only for the party to whom
it is addressed, and may contain information which is privileged
or confidential. Any other delivery, distribution, copying or
disclosure is strictly prohibited and is not a waiver of privilege
or confidentiality. If you have received this telecommunication in
error, please notify the sender immediately by return electronic
mail and destroy the message.
------------------------------------------------------------------------
--
=20
=20

Re: Reverse DNS Lookups

[Brian W. <bwe...@xb...>]

On Thu, 22 May 2003, J. Matthew Miller, III wrote:

> Hi,
>     I'm trying to work on some spam filtering software that uses dnsjava to
> do reverse DNS lookups using specific DNS servers.  Specifically, i'm using
> DNS Realtime Blackhole Lists (DNSRBL's).  Basically, the idea is that given
> a server, "permblock.easynet.net" -- and an ip address you want to check
> against that server's "known spammers list" (in this case, 69.1.80.67-- you
> do a lookup of "67.80.1.69.permblock.easynet.net."
> 
> Some DNS servers this works with, others it doesnt.  basically, any dns
> server i can't ping doesnt work.  I get an "UnknownHostException" thrown
> when i create a resolver.

Is the reason you can't ping the server that it doesn't exist?  You might 
want to use dig (or dnsjava's lookup program) to determine if the servers 
exist or not.

> Anyway, I'm wondering if there's a way around this that i'm not
> understanding, or if there's some limitation there, or if maybe i'm totally
> off base here.

If the server doesn't exist, there's no way you can send packets to it.

> Code is as follows:
> 
> ----------------------------
> 
> /*
>  * TestDNS.java
>  *
>  * Created on May 22, 2003, 2:03 PM
>  */
> import org.xbill.DNS.*;
> import java.net.*;
> import java.io.*;
> /**
>  *
>  * @author  matt
>  */
> public class TestDNS {
> 
>     /** Creates a new instance of TestDNS */
>     public TestDNS() {
>     }
>     public static void main(String args[]) {
>         try {
>             String[] dnslist = new String[1];
>             dnslist[0] = "permblock.easynet.net";
>             Resolver resolver = null;
>             try {
>                 resolver = new ExtendedResolver(dnslist);
>             } catch (UnknownHostException ee) {
>                 ee.printStackTrace();
>             }
>             Name name = null;
>             try {
>                 name = Name.fromString("67.80.1.69.permblock.easynet.net.");
>             } catch (Exception e) {
>                 e.printStackTrace();
>             }
>             Record question = Record.newRecord(name, Type.A, DClass.IN);
>             Message query = Message.newQuery(question);
>             Message response = null;
>             try {
>                 response = resolver.send(query);
>             }
>             catch (IOException e) {
>                 // A network error occurred.  Press on.
>                 e.printStackTrace();
>                 System.exit(0);
>             }
>             short rcode = response.getHeader().getRcode();
>             System.out.println("RCODE = " + rcode);
>         } catch (Exception e) {
>             e.printStackTrace();
>         }
> 
>     }
> 
> }

You'd be much better off using the Lookup class; something like:

	String[] dnslist = new String[1];
	dnslist[0] = "permblock.easynet.net";
	Resolver resolver = null;
	try {
		resolver = new ExtendedResolver(dnslist);
	} catch (UnknownHostException ee) {
		ee.printStackTrace();
	}
	Lookup lookup = new Lookup("67.80.1.69.permblock.easynet.net.");
	lookup.run();
	if (lookup.getResult() == Lookup.SUCCESSFUL)
		System.out.println("ok");
	else
		System.out.println("failed");

Brian

Reverse DNS Lookups

[J. M. M. I. <ma...@mo...>]

Hi,
    I'm trying to work on some spam filtering software that uses dnsjava to
do reverse DNS lookups using specific DNS servers.  Specifically, i'm using
DNS Realtime Blackhole Lists (DNSRBL's).  Basically, the idea is that given
a server, "permblock.easynet.net" -- and an ip address you want to check
against that server's "known spammers list" (in this case, 69.1.80.67-- you
do a lookup of "67.80.1.69.permblock.easynet.net."

Some DNS servers this works with, others it doesnt.  basically, any dns
server i can't ping doesnt work.  I get an "UnknownHostException" thrown
when i create a resolver.

Anyway, I'm wondering if there's a way around this that i'm not
understanding, or if there's some limitation there, or if maybe i'm totally
off base here.

Thanks for any help in advance,
    Matt Miller

Code is as follows:

----------------------------

/*
 * TestDNS.java
 *
 * Created on May 22, 2003, 2:03 PM
 */
import org.xbill.DNS.*;
import java.net.*;
import java.io.*;
/**
 *
 * @author  matt
 */
public class TestDNS {

    /** Creates a new instance of TestDNS */
    public TestDNS() {
    }
    public static void main(String args[]) {
        try {
            String[] dnslist = new String[1];
            dnslist[0] = "permblock.easynet.net";
            Resolver resolver = null;
            try {
                resolver = new ExtendedResolver(dnslist);
            } catch (UnknownHostException ee) {
                ee.printStackTrace();
            }
            Name name = null;
            try {
                name = Name.fromString("67.80.1.69.permblock.easynet.net.");
            } catch (Exception e) {
                e.printStackTrace();
            }
            Record question = Record.newRecord(name, Type.A, DClass.IN);
            Message query = Message.newQuery(question);
            Message response = null;
            try {
                response = resolver.send(query);
            }
            catch (IOException e) {
                // A network error occurred.  Press on.
                e.printStackTrace();
                System.exit(0);
            }
            short rcode = response.getHeader().getRcode();
            System.out.println("RCODE = " + rcode);
        } catch (Exception e) {
            e.printStackTrace();
        }

    }

}

Re: problems on setting resolver

[Georgine G. <cra...@ya...>]

Well, I don't thank you this time for your answer. In fact I did have to
specify the dns servers. And now it works just fine.

Geo

----- Original Message -----
From: "Brian Wellington" <bwe...@xb...>
To: "cradonge" <cra...@ya...>
Cc: <dns...@li...>
Sent: Thursday, April 10, 2003 7:54 PM
Subject: Re: problems on setting resolver


> On Thu, 10 Apr 2003, cradonge wrote:
>
> > Thanks for your answer. I've made changes you've told me. And I've got
> > no more exception. But I've got no result either. In fact I've got
> > result =2 (TRY_AGAIN). I've tried many times and always got the same
> > result.
> >
> > Here is my code:
> >
> > [snip]
> >
> > How can I know if my system is configured correctly?
>
> Try using another dns tool and see whether it fails also, like dig from
> bind 9.
>
> Brian

Re: problems on setting resolver

[Brian W. <bwe...@xb...>]

On Thu, 10 Apr 2003, cradonge wrote:

> Thanks for your answer. I've made changes you've told me. And I've got
> no more exception. But I've got no result either. In fact I've got
> result =2 (TRY_AGAIN). I've tried many times and always got the same
> result.
> 
> Here is my code:
> 
> [snip]
> 
> How can I know if my system is configured correctly?

Try using another dns tool and see whether it fails also, like dig from 
bind 9.

Brian

problems on setting resolver

[<cra...@ya...>]

Hi,

Thanks for your answer.
I've made changes you've told me. And I've got no more exception. But I've got no result either. In fact I've got result =2 (TRY_AGAIN). I've tried many times and always got the same result.

Here is my code:

[code on]

public static void dnslookup() throws UnknownHostException {

Lookup testl = null;
Record[] records = null;

try {
testl = new Lookup("yahoo.com", Type.MX);
records = testl.run();
}
catch (TextParseException e) {
System.out.println(e);}
System.out.println("result= " + testl.getResult());

if (records != null) {
Record record;
for (int i = 0; i < records.length; i++) {
record = records[i];
System.out.println("record= " + record.getName());
}
}
System.out.println("it's over");}

[code off]

How can I know if my system is configured correctly?

Geo.

 

 

 



---------------------------------
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Testez le nouveau Yahoo! Mail

Re: problems on setting resolver

[Brian W. <bwe...@xb...>]

On Tue, 8 Apr 2003, cradonge wrote:

> I'm trying to use dnsjava to validate email addresses. But I've got a
> lot of problems. So I will begin by the first one: how to set my dns
> servers.
> 
> This is my code:
> [code on]
> 
> Lookup testl = null;
> Record[] records = null;
> try {
> testl = new Lookup(www.yahoo.com);
> records = testl.run();
> } catch (TextParseException e) {
> System.out.println(e);}
> 
> [code off]

For one thing, this code won't compile, since www.yahoo.com needs to be 
quoted.  It also won't look for mail servers, since you don't specify a 
type to the Lookup constructor.

> I've got a NumberFormatException running this code. When I try to get
> the default resolver on the lookup, I've got the same error and when I
> try to set the default resolver either. I can't find any doc on which
> system properties I have to set.

There's no reason that this should throw a NumberFormatException.  Without 
seeing the actual exception and code, it's impossible to know why.

Neither setting a Resolver or setting system properties should be
necessary if your system is configured correctly.

> I'm sorry , I'm new to all this and maybe my question is stupid. But be
> kind and please answer me.

You don't provide enough information for the question to be answered.  If 
you provide more, I'll look into it.

Brian

problems on setting resolver

[<cra...@ya...>]

Hi,
I'm trying to use dnsjava to validate email addresses. But I've got a lot of problems. So I will begin by the first one: how to set my dns servers. 

This is my code:
[code on]

Lookup testl = null;
Record[] records = null;
try {
testl = new Lookup(www.yahoo.com);
records = testl.run();
} catch (TextParseException e) {
System.out.println(e);}

[code off]

I've got a NumberFormatException running this code. When I try to get the default resolver on the lookup, I've got the same error and when I try to set the default resolver either.
I can't find any doc on which system properties I have to set.

I'm sorry , I'm new to all this and maybe my question is stupid. But be kind and please answer me.

Thanks.

Geo.



---------------------------------
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Testez le nouveau Yahoo! Mail

Re: Getting an SMTP Server address from DNS

[Brian W. <bwe...@xb...>]

On Fri, 16 Aug 2002, Revathi Velu wrote:

> Hi,

> I browsed in one of the sites that hotmail has upto 14 smtp servers.  
> (As an example) While using dnsjava,
> 
>                         Record result[] =
> org.xbill.DNS.dns.getAnyRecords("hotmail.com", Type.MX);
>                         for (int i = 0 ; i<result.length ; i++ )
>                              {
> 
> System.out.println(result[i].rdataToString());
>                               }
> 
> gives me only 4 addresses. Am I doing the right thing. Pls correct me if I
> am wrong. I would appreciate some code samples.

It gives you 4 MX records.  Each MX record contains a name, not an 
address.  For example, one of them contains mx1.hotmail.com.  If you look 
up the addresses for mx1.hotmail.com, you'll find that there are 3 of 
them.

Brian

Re: Getting an SMTP Server address from DNS

[Revathi V. <rev...@ho...>]

Hi,
I browsed in one of the sites that hotmail has upto 14 smtp servers.  (As an
example)
While using dnsjava,

                        Record result[] =
org.xbill.DNS.dns.getAnyRecords("hotmail.com", Type.MX);
                        for (int i = 0 ; i<result.length ; i++ )
                             {

System.out.println(result[i].rdataToString());
                              }

gives me only 4 addresses. Am I doing the right thing. Pls correct me if I
am wrong. I would appreciate some code samples.
Thanks
Revathi




----- Original Message -----
From: "Brian Wellington" <bwe...@xb...>
To: "Revathi Velu" <rev...@ho...>
Sent: Thursday, February 27, 2003 3:07 PM
Subject: Re: Getting an SMTP Server address from DNS


> On Fri, 16 Aug 2002, Revathi Velu wrote:
>
> > Is ther a way to get a SMTP server address from the DNS name using
> > dnsjava ? Does the MXRecord
>
> Yes, you can query for an MX record.
>
> Questions should really be sent to the mailing list, not the admin
> address.
>
> Brian
>

Re: any doc?

[<bwe...@no...>]

On Fri, 31 Jan 2003, Hontvari Jozsef wrote:

> I cannot find any doc on the sourceforge site. I have seen the online docs
> on xbill.org, but it seems to me those aren't updated for a while.

Download the source.  Or read the documentation on www.xbill.org; the
javadoc is pretty much up-to-date.  I'll rebuild it now.

Brian

any doc?

[Hontvari J. <hon...@so...>]

I cannot find any doc on the sourceforge site. I have seen the online docs
on xbill.org, but it seems to me those aren't updated for a while.

Re: R: java.lang.outOfMemoryError

[Brian W. <bwe...@xb...>]

On Tue, 12 Nov 2002, Enrico Fustinoni wrote:

> Thank you for your response.
> I=92m using 1.3.0 version.=20
> I think that the problem is due to the high number of different domain
> in a very short time. So, the rate of new domain is greater than the
> rate of domain removed from the cache.
> I haven=92t seen all the dnsJava code jet, but I think that probably, a
> max number of domain to be cached need to be introduced so that the max
> amount of memory used by the application can be predetermined. Do you
> think I=92m right?

No, because the amount of memory per cached domain is not constant, so=20
limiting the cache based on the number of domains won't work as you'd=20
expect.

The ultimate correct solution is to make the cache cleaner more=20
aggressive, and more likely to successfully clean the entire cache withou=
t=20
getting an exception.  This means that the cache would need a new data=20
structure.

A good temporary solution would be to add a setMaxCache() function to the=
=20
Cache object, like the setMaxNCache() function.  Then you could set all=20
data to be cached for no more than, say, an hour, and the cache cleaner=20
would hopefully be able to remove more of it.

In any case, I won't have time to touch dnsjava code at all for the next=20
few weeks.

> In the next day, in my spare time, I=92ll try to better investigate the
> problem. =20

OK.

Brian

R: java.lang.outOfMemoryError

[Enrico F. <enr...@re...>]

Thank you for your response.
I=92m using 1.3.0 version.=20
I think that the problem is due to the high number of different domain
in a very short time. So, the rate of new domain is greater than the
rate of domain removed from the cache.
I haven=92t seen all the dnsJava code jet, but I think that probably, a
max number of domain to be cached need to be introduced so that the max
amount of memory used by the application can be predetermined. Do you
think I=92m right?

In the next day, in my spare time, I=92ll try to better investigate the
problem. =20

Enrico

=20



-----Messaggio originale-----
Da: dns...@li...
[mailto:dns...@li...] Per conto di Brian
Wellington
Inviato: luned=EC 11 novembre 2002 21.57
A: Enrico Fustinoni
Cc: dns...@li...
Oggetto: Re: java.lang.outOfMemoryError


On Mon, 11 Nov 2002, Enrico Fustinoni wrote:

> Once again, I renew my compliments for dnsJava and hits improvements.=20
> I'm performing some test, so I wrote e program that finds the=20
> authoritative name server for a set of domains. After 45108 DNS query=20
> on different domains in about 4.5 hours the program stop with a=20
> java.lang.outOfMemoryError. I started the java virtual machine with=20
> java -Xmx100000000 -Xss10000000.
>=20
> After looking the code, I think that this problem is due to an=20
> excessive use of memory from the cache class.

What version of dnsjava?  1.3.0 uses a lot less memory than 1.2.4, and
is=20
better about removing expired data.

> Is this possible? Is there anything I can do to solve this problem?

If you're using 1.2.4, upgrade.  If you're using 1.3.0, I'm not really=20
sure.

Brian



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
dnsjava-users mailing list
dns...@li...
https://lists.sourceforge.net/lists/listinfo/dnsjava-users

Re: java.lang.outOfMemoryError

[Brian W. <bwe...@xb...>]

On Mon, 11 Nov 2002, Enrico Fustinoni wrote:

> Once again, I renew my compliments for dnsJava and hits improvements.
> I'm performing some test, so I wrote e program that finds the
> authoritative name server for a set of domains.
> After 45108 DNS query on different domains in about 4.5 hours the
> program stop with a java.lang.outOfMemoryError.
> I started the java virtual machine with java -Xmx100000000 -Xss10000000.
> 
> After looking the code, I think that this problem is due to an excessive
> use of memory from the cache class.

What version of dnsjava?  1.3.0 uses a lot less memory than 1.2.4, and is 
better about removing expired data.

> Is this possible? Is there anything I can do to solve this problem?

If you're using 1.2.4, upgrade.  If you're using 1.3.0, I'm not really 
sure.

Brian

java.lang.outOfMemoryError

[Enrico F. <enr...@re...>]

Once again, I renew my compliments for dnsJava and hits improvements.
I'm performing some test, so I wrote e program that finds the
authoritative name server for a set of domains.
After 45108 DNS query on different domains in about 4.5 hours the
program stop with a java.lang.outOfMemoryError.
I started the java virtual machine with java -Xmx100000000 -Xss10000000.

After looking the code, I think that this problem is due to an excessive
use of memory from the cache class.

Is this possible? Is there anything I can do to solve this problem?

Thanks for your interest.

 

Enrico

dnsjava 1.3.0 released

[Brian W. <bwe...@xb...>]

I released dnsjava 1.3.0.  It's basically the same as the beta, with one 
bug fix to the cache cleaner, a minor optimization to the cache, and the 
Name.getLabel() function.

There are a bunch of optimizations to both speed and memory usage and a
number of bug fixes since 1.2.4.  A lot of internal code was updated to
use Collections, so Java 1.2 or greater is now required.  Large portions
of code have been completely rewritten (Name.java, for example), and the
new code is a lot more sane and has a cleaner API.

Changelog below.

Brian

--------
10/16/2002
        - 1.3.0 released.

10/11/2002
        - Add Name.getLabel()

10/10/2002
        - When cleaning the cache, catch ConcurrentModificationExceptions.

10/8/2002
	- Cleanups to Cache.addMessage() and the Credibility code.

10/7/2002
	- Fix problems with search path handling in the dns class.
	- Possible race condition fixes to the Cache code.

10/6/2002
	- Fix minor bugs in Name code (Bob Halley <bob...@no...>)
	  
10/1/2002
	- Memory usage and speed improvements to the TypeMap class.

9/25/2002
	- Add the verbosecache option.
	- Significant memory usage improvements to the Name class.

9/23/2002
	- Memory usage improvements to the ARecord class.

9/16/2002
	- Support for NetWare's sys:/etc/resolv.cfg file.
	  (Scott Villinski <sc...@vi...>)

9/5/2002
	- When looking for an rdataset in a zone or cache, seeing a CNAME
	  above the name is not an error.
	  (reported by Andrew Houghton <aa...@vo...>)

8/31/2002
	- Changed the code that dynamically loads record types; hopefully
	  this will solve some of the mysterious problems that I think
	  are related to non-English versions of Windows.
	- Clean up the Name code.

8/28/2002
	- Remove support for bitstring labels, since they're now deprecated.

8/16/2002
	- Address.isDottedQuad didn't check to see if the input String
	  contained characters after an IP address.
	  (Marcos Sanz <sa...@de...>)

8/11/2002
	- Querying for a nonexistant name with exactly one label didn't return.

8/10/2002
	- Add Ant build script (Blake Ramsdell <bl...@br...>)

8/6/2002
	- The AAAARecord constructor was broken.
	- The Record class now implements Comparable.

6/22/2002
	- Significant speed improvements in the Record class and its
	  subclasses.

6/20/2002
	- Add Zone.removeRecord() (based on code from Adam Cassar
	  <ada...@ne...>)
	- Add Zone.toMasterFile() (based on code from Adam Cassar)
	- Performance enhancements to the Name object.
	- Add the "-t type" option to the lookup program.

6/16/2002
	- Update lots of code to use Collections instead of JDK 1.1
	  Vectors & Hashtables.

5/28/2002
	- fix some limitations of name parsing.
	  (reported by Tasos Kotsikonas <ta...@bo...>)

5/4/2002
	- added the 'sleep' and 'date' commands to the update client.
	  (Olafur Gudmundsson <og...@og...>)

dnsjava 1.3.0 released

[Brian W. <bwe...@xb...>]

I released dnsjava 1.3.0.  It's basically the same as the beta, with one 
bug fix to the cache cleaner, a minor optimization to the cache, and the 
Name.getLabel() function.

There are a bunch of optimizations to both speed and memory usage and a
number of bug fixes since 1.2.4.  A lot of internal code was updated to
use Collections, so Java 1.2 or greater is now required.  Large portions
of code have been completely rewritten (Name.java, for example), and the
new code is a lot more sane and has a cleaner API.

Changelog below.

Brian

--------
10/16/2002
        - 1.3.0 released.

10/11/2002
        - Add Name.getLabel()

10/10/2002
        - When cleaning the cache, catch ConcurrentModificationExceptions.

10/8/2002
	- Cleanups to Cache.addMessage() and the Credibility code.

10/7/2002
	- Fix problems with search path handling in the dns class.
	- Possible race condition fixes to the Cache code.

10/6/2002
	- Fix minor bugs in Name code (Bob Halley <bob...@no...>)
	  
10/1/2002
	- Memory usage and speed improvements to the TypeMap class.

9/25/2002
	- Add the verbosecache option.
	- Significant memory usage improvements to the Name class.

9/23/2002
	- Memory usage improvements to the ARecord class.

9/16/2002
	- Support for NetWare's sys:/etc/resolv.cfg file.
	  (Scott Villinski <sc...@vi...>)

9/5/2002
	- When looking for an rdataset in a zone or cache, seeing a CNAME
	  above the name is not an error.
	  (reported by Andrew Houghton <aa...@vo...>)

8/31/2002
	- Changed the code that dynamically loads record types; hopefully
	  this will solve some of the mysterious problems that I think
	  are related to non-English versions of Windows.
	- Clean up the Name code.

8/28/2002
	- Remove support for bitstring labels, since they're now deprecated.

8/16/2002
	- Address.isDottedQuad didn't check to see if the input String
	  contained characters after an IP address.
	  (Marcos Sanz <sa...@de...>)

8/11/2002
	- Querying for a nonexistant name with exactly one label didn't return.

8/10/2002
	- Add Ant build script (Blake Ramsdell <bl...@br...>)

8/6/2002
	- The AAAARecord constructor was broken.
	- The Record class now implements Comparable.

6/22/2002
	- Significant speed improvements in the Record class and its
	  subclasses.

6/20/2002
	- Add Zone.removeRecord() (based on code from Adam Cassar
	  <ada...@ne...>)
	- Add Zone.toMasterFile() (based on code from Adam Cassar)
	- Performance enhancements to the Name object.
	- Add the "-t type" option to the lookup program.

6/16/2002
	- Update lots of code to use Collections instead of JDK 1.1
	  Vectors & Hashtables.

5/28/2002
	- fix some limitations of name parsing.
	  (reported by Tasos Kotsikonas <ta...@bo...>)

5/4/2002
	- added the 'sleep' and 'date' commands to the update client.
	  (Olafur Gudmundsson <og...@og...>)

Re: ConcurrentModificationException

[Brian W. <bwe...@xb...>]

On Thu, 10 Oct 2002, Brian Wellington wrote:

> > Just going through some servlet logs and found this:
> > 
> > java.util.ConcurrentModificationException
> > 	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:750)
> > 	at java.util.HashMap$KeyIterator.next(HashMap.java:786)
> > 	at org.xbill.DNS.Cache$CacheCleaner.clean(Cache.java:120)
> > 	at org.xbill.DNS.Cache$CacheCleaner.run(Cache.java:152)
> > 
> > I'm using the 1.3.0 beta; I have no context information and no idea what 
> > it was I did that led to this (sorry), but I thought it might be useful 
> > if I passed this info on.
> > 
> > For what it's worth, I've got lots of little threads doing DNS lookups 
> > at various times, but this exception seems to be a lower level problem.
> 
> Thanks.  I can reproduce this by running a program which does a lot of 
> queries in combination with aggressive cache cleaning, so it shouldn't be 
> too hard to fix.

OK, fixed.  You can either get the current code from CVS, or just modify 
Cache.java::CacheCleaner::clean() to catch ConcurrentModificationException 
around the iterator.

Brian

Re: ConcurrentModificationException

[Brian W. <bwe...@xb...>]

On Thu, 10 Oct 2002, Andrew Houghton wrote:

> Just going through some servlet logs and found this:
> 
> java.util.ConcurrentModificationException
> 	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:750)
> 	at java.util.HashMap$KeyIterator.next(HashMap.java:786)
> 	at org.xbill.DNS.Cache$CacheCleaner.clean(Cache.java:120)
> 	at org.xbill.DNS.Cache$CacheCleaner.run(Cache.java:152)
> 
> I'm using the 1.3.0 beta; I have no context information and no idea what 
> it was I did that led to this (sorry), but I thought it might be useful 
> if I passed this info on.
> 
> For what it's worth, I've got lots of little threads doing DNS lookups 
> at various times, but this exception seems to be a lower level problem.

Thanks.  I can reproduce this by running a program which does a lot of 
queries in combination with aggressive cache cleaning, so it shouldn't be 
too hard to fix.

This would have turned up sooner had earlier versions properly started the 
cache cleaner.  Sigh.

Brian

ConcurrentModificationException

[Andrew H. <aa...@vo...>]

Just going through some servlet logs and found this:

java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:750)
	at java.util.HashMap$KeyIterator.next(HashMap.java:786)
	at org.xbill.DNS.Cache$CacheCleaner.clean(Cache.java:120)
	at org.xbill.DNS.Cache$CacheCleaner.run(Cache.java:152)

I'm using the 1.3.0 beta; I have no context information and no idea what 
it was I did that led to this (sorry), but I thought it might be useful 
if I passed this info on.

For what it's worth, I've got lots of little threads doing DNS lookups 
at various times, but this exception seems to be a lower level problem.

- a.