From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Authoritative Name Server
Date: Wed, 16 Sep 2009 19:37:20 -0400 [thread overview]
Message-ID: <fe41879c0909161637n18a66778u6e6a9e64e0fd7823@mail.gmail.com> (raw)
In-Reply-To: <350d8ffb1d47ad2f876620e6381ebcca@yyc.orthanc.ca>
Thanks. This is all fine, now.
The remaining problem is regarding my earlier post about
SRV records. Using ndb/dnsquery, I get proper output:
cpu% ndb/dnsquery
> _jabber._tcp.mail.nanosouffle.net srv
_jabber._tcp.mail.nanosouffle.net srv 5 0 5269 xmpp-server.l.google.com
_jabber._tcp.mail.nanosouffle.net srv 20 0 5269 xmpp-server1.l.google.com
_jabber._tcp.mail.nanosouffle.net srv 20 0 5269 xmpp-server2.l.google.com
_jabber._tcp.mail.nanosouffle.net srv 20 0 5269 xmpp-server3.l.google.com
_jabber._tcp.mail.nanosouffle.net srv 20 0 5269 xmpp-server4.l.google.com
However, using dig, there is a problem:
linux$ dig @ns1.nanosouffle.net _jabber._tcp.mail.nanosouffle.net srv
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.5.0a6 <<>> @ns1.nanosouffle.net
_jabber._tcp.mail.nanosouffle.net srv
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14236
;; flags: qr aa ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Messages has 207 extra bytes at end
;; QUESTION SECTION:
;_jabber._tcp.mail.nanosouffle.net. IN SRV
;; Query time: 5 msec
;; SERVER: 75.58.233.40#53(75.58.233.40)
;; WHEN: Wed Sep 16 16:17:54 2009
;; MSG SIZE rcvd: 270
The relevant portion of the ndb file looks like this:
dom=_jabber._tcp.mail.nanosouffle.net
srv=xmpp-server.l.google.com pri=5 weight=0 port=5269
srv=xmpp-server1.l.google.com pri=20 weight=0 port=5269
srv=xmpp-server2.l.google.com pri=20 weight=0 port=5269
srv=xmpp-server3.l.google.com pri=20 weight=0 port=5269
srv=xmpp-server4.l.google.com pri=20 weight=0 port=5269
Ideas?
ak
next prev parent reply other threads:[~2009-09-16 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 19:31 Akshat Kumar
2009-09-16 20:03 ` erik quanstrom
2009-09-16 20:37 ` Akshat Kumar
2009-09-16 20:51 ` erik quanstrom
2009-09-16 22:47 ` Akshat Kumar
2009-09-16 23:02 ` Akshat Kumar
2009-09-16 23:05 ` erik quanstrom
2009-09-16 23:25 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-16 23:37 ` Akshat Kumar [this message]
2009-09-16 23:40 ` erik quanstrom
2009-09-16 23:58 ` Akshat Kumar
2009-09-16 23:47 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-16 23:52 ` Akshat Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe41879c0909161637n18a66778u6e6a9e64e0fd7823@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).