[Pdns-users] Pdns-users Digest, Vol 116, Issue 2

Seema Datar sdatar at yahoo-inc.com
Tue Sep 4 03:59:51 UTC 2012




On 9/3/12 8:05 PM, "Seema Datar" <sdatar at yahoo-inc.com> wrote:

> 
> Hi Peter,
> 
> Thanks for the response. Which one of these lists should I send questions
> to?
> 
> To clarify the question further -
> 
> With the DSEC option, I see 2 packets returned probably because it does not
> understand the option. If you notice, " m.root-servers.net" appears in the
> second part of the response. This is a response to a single dig query. The
> part which does contain " m.root-servers.net" does not have an ANSWER
> section. The forst part which has the ANSWER section has entries only upto
> l.root-servers.net. In PDNS-2.99.2, I did not see this difference.
> 
> 
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.1 <<>> @localhost xxx DSEC
> ; (1 server found)
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30600
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 12
> 
> ;; QUESTION SECTION:
> ;xxx. IN    A
> 
> ;; ANSWER SECTION:
> xxx. 300 IN CNAME    xxx.y.com.
> 
> ;; AUTHORITY SECTION:
> .            518400    IN    NS    a.root-servers.net.
> .            518400    IN    NS    b.root-servers.net.
> .            518400    IN    NS    c.root-servers.net.
> .            518400    IN    NS    d.root-servers.net.
> .            518400    IN    NS    e.root-servers.net.
> .            518400    IN    NS    f.root-servers.net.
> .            518400    IN    NS    g.root-servers.net.
> .            518400    IN    NS    h.root-servers.net.
> .            518400    IN    NS    i.root-servers.net.
> .            518400    IN    NS    j.root-servers.net.
> .            518400    IN    NS    k.root-servers.net.
> .            518400    IN    NS    l.root-servers.net.
> .            518400    IN    NS    m.root-servers.net.
> 
> ;; ADDITIONAL SECTION:
> a.root-servers.net.    3600000    IN    A    192.1.1.1
> b.root-servers.net.    3600000    IN    A    192.1.1.2
> c.root-servers.net.    3600000    IN    A    192.1.1.3
> d.root-servers.net.    3600000    IN    A    192.1.1.4
> e.root-servers.net.    3600000    IN    A    192.1.1.5
> f.root-servers.net.    3600000    IN    A    192.1.1.6
> g.root-servers.net.    3600000    IN    A    192.1.1.7
> h.root-servers.net.    3600000    IN    A    192.1.1.8
> i.root-servers.net.    3600000    IN    A    192.1.1.9
> j.root-servers.net.    3600000    IN    A    192.1.1.10
> k.root-servers.net.    3600000    IN    A    192.1.1.11
> l.root-servers.net.    3600000    IN    A    192.1.1.12
> 
> ;; Query time: 4 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Mon Sep  3 07:28:41 2012
> ;; MSG SIZE  rcvd: 477
> 
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19923
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13
> 
> ;; QUESTION SECTION:
> ;DSEC.                IN    A
> 
> ;; AUTHORITY SECTION:
> .            518400    IN    NS    a.root-servers.net.
> .            518400    IN    NS    b.root-servers.net.
> .            518400    IN    NS    c.root-servers.net.
> .            518400    IN    NS    d.root-servers.net.
> .            518400    IN    NS    e.root-servers.net.
> .            518400    IN    NS    f.root-servers.net.
> .            518400    IN    NS    g.root-servers.net.
> .            518400    IN    NS    h.root-servers.net.
> .            518400    IN    NS    i.root-servers.net.
> .            518400    IN    NS    j.root-servers.net.
> .            518400    IN    NS    k.root-servers.net.
> .            518400    IN    NS    l.root-servers.net.
> .            518400    IN    NS    m.root-servers.net.
> 
> ;; ADDITIONAL SECTION:
> a.root-servers.net.    3600000    IN    A    192.1.1.1
> b.root-servers.net.    3600000    IN    A    192.1.1.2
> c.root-servers.net.    3600000    IN    A    192.1.1.3
> d.root-servers.net.    3600000    IN    A    192.1.1.4
> e.root-servers.net.    3600000    IN    A    192.1.1.5
> f.root-servers.net.    3600000    IN    A    192.1.1.6
> g.root-servers.net.    3600000    IN    A    192.1.1.7
> h.root-servers.net.    3600000    IN    A    192.1.1.8
> i.root-servers.net.    3600000    IN    A    192.1.1.9
> j.root-servers.net.    3600000    IN    A    192.1.1.10
> k.root-servers.net.    3600000    IN    A    192.1.1.11
> l.root-servers.net.    3600000    IN    A    192.1.1.12
> m.root-servers.net.    3600000    IN    A    192.1.1.13
> 
> ;; Query time: 3 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Mon Sep  3 07:28:41 2012
> ;; MSG SIZE  rcvd: 441
> 
> Thanks,
> Seema
> 
> 
> 
> On 9/3/12 3:30 PM, "pdns-users-request at mailman.powerdns.com"
> <pdns-users-request at mailman.powerdns.com> wrote:
> 
>> Send Pdns-users mailing list submissions to
>> pdns-users at mailman.powerdns.com
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://mailman.powerdns.com/mailman/listinfo/pdns-users
>> or, via email, send a message with subject or body 'help' to
>> pdns-users-request at mailman.powerdns.com
>> 
>> You can reach the person managing the list at
>> pdns-users-owner at mailman.powerdns.com
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Pdns-users digest..."
>> 
>> 
>> Today's Topics:
>> 
>>    1. Question regarding the additional section (Seema Datar)
>>    2. Re: Question regarding the additional section (Peter van Dijk)
>>    3. Re: Strange pdns-recursor crash (Peter van Dijk)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Mon, 3 Sep 2012 11:03:30 +0530
>> From: Seema Datar <sdatar at yahoo-inc.com>
>> Subject: [Pdns-users] Question regarding the additional section
>> To: "pdns-dev at mailman.powerdns.com" <pdns-dev at mailman.powerdns.com>
>> Cc: "pdns-users at mailman.powerdns.com"
>> <pdns-users at mailman.powerdns.com>
>> Message-ID: <CC6A3F02.37DAC%sdatar at yahoo-inc.com>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> Hi,
>> 
>> I had a question regarding the MSG size in PDNS v3. I see that when the
>> query does not result in an answer section, the ADDITONAL section is
>> complete with all the entries and the MSG size happens to be 437. However,
>> when the answer section exists, it skips some of the entries in the
>> ADDITIONAL section and the total MSG size is limited to 477.
>> 
>> I did not see this behavior in PDNS v2. The question is, in the v3 version,
>> is the message size being limited which results in certain entries being
>> skipped in the ADDITIONAL section?
>> 
>> 
>> Thanks,
>> Seema
>> 
>> 
>> 
>> 
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Mon, 3 Sep 2012 09:11:01 +0200
>> From: Peter van Dijk <peter.van.dijk at netherlabs.nl>
>> Subject: Re: [Pdns-users] Question regarding the additional section
>> To: pdns-users Users <pdns-users at mailman.powerdns.com>
>> Message-ID: <5B79431D-1D47-48BA-BE4B-5844F8BBFA0B at netherlabs.nl>
>> Content-Type: text/plain; charset=us-ascii
>> 
>> Hello Seema,
>> 
>> please don't post to both lists. We'd rather have a question on the wrong
>> list
>> than a thread split between both lists.
>> 
>> On Sep 3, 2012, at 7:33 , Seema Datar wrote:
>> 
>>> I had a question regarding the MSG size in PDNS v3. I see that when the
>>> query does not result in an answer section, the ADDITONAL section is
>>> complete with all the entries and the MSG size happens to be 437. However,
>>> when the answer section exists, it skips some of the entries in the
>>> ADDITIONAL section and the total MSG size is limited to 477.
>>> 
>>> I did not see this behavior in PDNS v2. The question is, in the v3 version,
>>> is the message size being limited which results in certain entries being
>>> skipped in the ADDITIONAL section?
>> 
>> 
>> I'd be happy to look into this, but it would help if you had concrete
>> examples, preferably from the same zone. Can you provide this?
>> 
>> Kind regards,
> 




More information about the Pdns-users mailing list