Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • From what I can gather, the problem is something to do with pm.org's nameserver not delgating correctly.
    dig @193.82.57.128 london.pm.org
    Works fine

    Paul Makepeace is on the problem as sorting it out. Have faith that it will be resolved.

    Sorry for the Delay.

  • ns through ns3.develooper.com are all sending malformed DNS responses.  Any sane DNS server will reject such malformed packets.

    twilde@manganese:~$ dig london.pm.org. @ns.develooper.com. +short
    ;; Warning: Message parser reports malformed message packet.
    193.82.57.128

    That way gets the address, but my caching server won't accept the malformed responses to give me DNS - any version of BIND will exhibit that behavior.  Track down the malformed responses and it should work fine.
  • it'd be infinitely more efficient to email me or dns@pm.org than to write about it here. :-)

      - ask
    --

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();

    • I thought that Paul Makepeace was sorting it out and talking to dns@pm.org. Anyway, Wayne has been busy and this is all about a lack of communication hence my journal post.