[Pdns-users] Apologies + Memory hitch in Windows
mloftis at wgops.com
Thu Jan 5 05:03:30 UTC 2006
--On December 18, 2005 6:46:34 PM +0000 MRJ InfoTech Admin
<admin at mrjdesign.net> wrote:
> First of all, my apologies to the lot who received my posts to the wrong
> I apparently misread the initial sign up page and the messages following,
> I assumed was getting into this group and nowhere else.
> Now, for something much more mission critical.
> Having battled a few minor bugs, I have finally managed to make PDNS work
> on my PC running Windows XP Pro SP1.
> My configuration is as follows.
> Workstation for testing:
> Windows XP Pro SP1, 1 GB RAM and 2 GB free space on D-drive where
> PDNS resides.
> Server for deployment:
> Windows XP Pro SP1, 512 Mb RAM, 160 GB free space on MX/ DNS drive
> Upon my initial tests I have had no problems with the server running
> simultaneous to my browser and other applications.
> After inserting an RP value into the MDB file, I came upon a very odd
> The memory Commit Charge is running up form the regular 191 MB to over
> 1200 MB.
Windows is probably not very well tested, and from other clues it sounds
like you're using MS Access as a 'database.' MS Access is not suitable for
any production use in any situation in my experience. I'd recomment using
MSSQL or MySQL (Even with the Windows ODBC drivers).
> I assume this is caused by PDNS not understanding the message I inserted
> in the RP value, or when other values are erroneous as well.
> I would like for this purpose to know, if anyone could tell me exactly
> how the RP value should be inserted to
> test this theory of mine, and discard any fears of PDNS not being
> properly working on my windows box.
> The value I had inserted was the following.
I have NO idea what an 'RP' record is. type is the type of DNS record.
CNAME, A, PTR, NS, SOA, MX (which is where prio comes in), and TXT are all
valid types, there might be others as well. Further domain_id is the
matching id number from the domains table, and probably is never, and
probabyl should never, be 0. That shouldn't cause a leak though, just a
total failure to find the record, though...I guess that depends on your sql
A further piece of information that'll be usefel/necessary is the PDNS
version you're using.
> Of course, a bunch of other values too but they are irrelevant as the
> application worked before this.
> MRJ Information Technology Ltd.
> 35 Camden High St., Camden/London, NW1 7JE
> United Kingdom http://www.mrjdesign.net
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
More information about the Pdns-users