[Juser] Changes due to Denial of Service Attacks

Kevin Smith kevin at kismith.co.uk
Wed Sep 5 07:05:00 UTC 2012


On Wed, Sep 5, 2012 at 1:37 AM, Rob Newton <robn at mirrabooka.com> wrote:
> On 05/09/12 03:05, Kevin Smith wrote:
>
> On Tue, Sep 4, 2012 at 12:43 AM, Rob Newton <robn at mirrabooka.com> wrote:
>
> Since the recent denial of service attacks, I understand that some measures
> were taken on the server side to prevent the attacks.  In particular, this
> notice:
>
> Below is the debug log.  Can anyone see what the problem might be?  Would it
> be that Pidgin doesn't handle DNS SRV records correctly?
>
> It's not that Pidgin doesn't support SRV (I believe it does) but that
> either it's configured not to use it, or the DNS servers it's using
> are broken.
>
> (09:33:21) proxy: Attempting connection to 208.68.163.220
> (09:33:21) proxy: Connecting to jabber.org:5222 with no proxy
>
> This is, as you surmised, not trying SRV.
>
> So either somewhere in the account config in Pidgin you'll find that
> you've got it set with a manual connect host of jabber.org, port 5222,
> or running
>
> dig -t srv _xmpp-client._tcp.jabber.org
>
> won't give you the three results it should.
>
> Yes,  I had it misconfigured.  Now I do have it trying SRV:
>
> (10:31:45) dnssrv: querying SRV record for jabber.org:
> _xmpp-client._tcp.jabber.org
> (10:31:55) dnssrv: res_query returned an error
>
> # dig -t srv _xmpp-client._tcp.jabber.org
>
> ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.2.rc1.fc16 <<>> -t srv
> _xmpp-client._tcp.jabber.org
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached
>
>
> Your dig command suggests a fundamental problem.  Could it be that my home
> router/modem is blocking something?  Or my ISP?  Certainly I'm not having
> any other DNS problems.

Either of these, yes. I think it's more likely your router has a
broken DNS server on it. Switching your machines to use known-good
servers instead of your router is what I'd probably do.

/K


More information about the JUser mailing list