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
