Adding more nameservers will not help performance (unless the first two
are down of course).
This 'feels' like a network issue to me. I've seen this sort of problem
caused by errant routing table entries. If there's an entry which points
to a bogus interface, that can cause delays. Check your routing table
('route' command), and you might want to do a few traceroutes
('traceroute' command) to see if you can pinpoint where the delay is
occurring.
Peter Tan wrote:
Thanks Jake, I'll check with the server co-location provider. Google and
Yahoo have servers here in Malaysia, it shouldn't be that slow.
I'm also going to add more NS to the domain. Do you think it will help?
Currently, there's only 2 NS.
On Wed, Sep 2, 2009 at 8:51 PM, Jake Vickers <[email protected]
<mailto:[email protected]>> wrote:
Peter Tan wrote:
I'm using djbdns.
2 lines in resolv.conf:
search myservername.com <http://myservername.com>
nameserver 127.0.0.1
dig qmailtoaster.com <http://qmailtoaster.com>
; <<>> DiG 9.3.4-P1 <<>> qmailtoaster.com <http://qmailtoaster.com>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47062
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;qmailtoaster.com <http://qmailtoaster.com>. IN A
;; ANSWER SECTION:
qmailtoaster.com <http://qmailtoaster.com>. 86400 IN
A 216.81.238.95
;; Query time: 1301 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 2 19:50:32 2009
;; MSG SIZE rcvd: 50
dig google.com <http://google.com>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18032
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com <http://google.com>. IN A
;; ANSWER SECTION:
google.com <http://google.com>. 300 IN A
74.125.67.100
google.com <http://google.com>. 300 IN A
74.125.45.100
google.com <http://google.com>. 300 IN A
74.125.127.100
;; Query time: 261 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 2 19:52:01 2009
;; MSG SIZE rcvd: 76
dig yahoo.com <http://yahoo.com>
; <<>> DiG 9.3.4-P1 <<>> yahoo.com <http://yahoo.com>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2661
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;yahoo.com <http://yahoo.com>. IN A
;; ANSWER SECTION:
yahoo.com <http://yahoo.com>. 21600 IN A
209.131.36.159
yahoo.com <http://yahoo.com>. 21600 IN A
209.191.93.53
yahoo.com <http://yahoo.com>. 21600 IN A
69.147.114.224
;; Query time: 130 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 2 19:53:38 2009
;; MSG SIZE rcvd: 75
Pop3 and SMTP slow during session/transfer, especially with
attachments.
Either you have a real slow Internet connection, or something is
going on with your DNS.
The item to note is the "Query time". For qmailtoaster.com
<http://qmailtoaster.com> I get 20ms. For google.com
<http://google.com> I get 15ms. For yahoo.com <http://yahoo.com> I
get 5ms. I tried from 3 other servers as well (spread across the
United States, on both coasts) and the highest result I had was 70ms.
Your best one was 130ms, and Yahoo runs a *fast* DNS network.
Try doing a file transfer on that machine as well - if everything is
slow then you may have a network issue or some other underlying issue.
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
