XMailforum is a readonly knowledge archive now.

Registering as a new user or answering posts is not possible anymore.

Might the force be with you, to find here what you are looking for.

2019-09-20 - hschneider, Admin

Cookie Disclaimer: This forum uses only essential, anonymous session cookies (xmailforum*), nothing to be scared of.

XMail Forum -> Maximum Dns Quesry Depth Exceeded

Reply to this topicStart new topicStart Poll

> Maximum Dns Quesry Depth Exceeded, [SOLVED]Dig +trace = "Too many lookups"
BizOdd
Posted: Mar 11 2009, 05:54 PM
Quote Post


Member
***

Group: Members
Posts: 58
Member No.: 1386
Joined: 1-November 04



Hi Guys,
Im trying to work out why my servers cant seem to send
email to 'info@greatnorthernsnowcat.com' about 90% of the time
(some do seem to sneak by occasionally)

the slog error is:
[PeekTime] 1236702251 : Tue, 10 Mar 2009 12:24:11 -0400
<<
ErrCode = -253
ErrString = Maximum DNS quesry depth exceeded
ErrInfo = greatnorthernsnowcat.com
Recipient domain "greatnorthernsnowcat.com" does not exist (or it has a misconfigured DNS)
>>

If i run the following command on my server:
dig MX greatnorthernsnowcat.com +trace
the dig command runs for a few seconds and comes back with:
dig: too many lookups

I dont know that much about DNS, could someone knowledgeable explain that
error to me, so I can explain it to the domain owner (who assures me only
my server has problems sending to them)

Or, does anyone know a way to trick the xmail server into always sending email
for greatnorthernsnowcat.com to a specified ip address and not perform and DNS queries?

thanks
BizOdd
PMEmail Poster
Top
BizOdd
Posted: Mar 16 2009, 08:05 PM
Quote Post


Member
***

Group: Members
Posts: 58
Member No.: 1386
Joined: 1-November 04



Im Getting the exact same error for
purvismarine.com now also.

-BizOdd
PMEmail Poster
Top
jobber_jobber
Posted: Mar 17 2009, 02:49 AM
Quote Post


Newbie
*

Group: Members
Posts: 19
Member No.: 1307
Joined: 13-September 04



Hi,

I'm afraid it does seem to be something to do with the way your system is resolving DNS queries: if I try those commands on my server, I get this:

$ dig MX greatnorthernsnowcat.com +trace

; <<>> DiG 9.4.2-P2 <<>> MX greatnorthernsnowcat.com +trace
;; global options: printcmd
. 257485 IN NS F.ROOT-SERVERS.NET.
. 257485 IN NS M.ROOT-SERVERS.NET.
. 257485 IN NS I.ROOT-SERVERS.NET.
. 257485 IN NS A.ROOT-SERVERS.NET.
. 257485 IN NS K.ROOT-SERVERS.NET.
. 257485 IN NS E.ROOT-SERVERS.NET.
. 257485 IN NS B.ROOT-SERVERS.NET.
. 257485 IN NS H.ROOT-SERVERS.NET.
. 257485 IN NS J.ROOT-SERVERS.NET.
. 257485 IN NS D.ROOT-SERVERS.NET.
. 257485 IN NS L.ROOT-SERVERS.NET.
. 257485 IN NS G.ROOT-SERVERS.NET.
. 257485 IN NS C.ROOT-SERVERS.NET.
;; Received 500 bytes from xxx.xxx.xxx.xxx#53(xxx.xxx.xxx.xxx) in 17 ms

com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 502 bytes from 199.7.83.42#53(L.ROOT-SERVERS.NET) in 148 ms

greatnorthernsnowcat.com. 172800 IN NS ns100.webmasters.com.
greatnorthernsnowcat.com. 172800 IN NS ns101.webmasters.com.
;; Received 125 bytes from 192.52.178.30#53(k.gtld-servers.net) in 38 ms

greatnorthernsnowcat.com. 86400 IN MX 10 mail.greatnorthernsnowcat.com.
greatnorthernsnowcat.com. 86400 IN NS ns100.webmasters.com.
greatnorthernsnowcat.com. 86400 IN NS ns101.webmasters.com.
;; Received 130 bytes from 208.64.136.91#53(ns101.webmasters.com) in 135 ms



$ dig MX purvismarine.com +trace


; <<>> DiG 9.4.2-P2 <<>> MX purvismarine.com +trace
;; global options: printcmd
. 257463 IN NS F.ROOT-SERVERS.NET.
. 257463 IN NS J.ROOT-SERVERS.NET.
. 257463 IN NS D.ROOT-SERVERS.NET.
. 257463 IN NS E.ROOT-SERVERS.NET.
. 257463 IN NS K.ROOT-SERVERS.NET.
. 257463 IN NS M.ROOT-SERVERS.NET.
. 257463 IN NS H.ROOT-SERVERS.NET.
. 257463 IN NS A.ROOT-SERVERS.NET.
. 257463 IN NS G.ROOT-SERVERS.NET.
. 257463 IN NS C.ROOT-SERVERS.NET.
. 257463 IN NS I.ROOT-SERVERS.NET.
. 257463 IN NS B.ROOT-SERVERS.NET.
. 257463 IN NS L.ROOT-SERVERS.NET.
;; Received 500 bytes from xxx.xxx.xxx.xxx#53(xxx.xxx.xxx.xxx) in 0 ms

com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
;; Received 506 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 25 ms

purvismarine.com. 172800 IN NS icewall.vianet.on.ca.
purvismarine.com. 172800 IN NS trafficcop.pictographics.com.
;; Received 123 bytes from 192.54.112.30#53(H.GTLD-SERVERS.NET) in 33 ms

purvismarine.com. 20 IN MX 20 mail2.pictographics.com.
purvismarine.com. 20 IN MX 9 mail.pictographics.com.
purvismarine.com. 86400 IN NS trafficcop.pictographics.com.
purvismarine.com. 86400 IN NS icewall.vianet.on.ca.
;; Received 182 bytes from 205.207.184.102#53(trafficcop.pictographics.com) in 133 ms

Wish I could help you with the xmail question though, but it might be better to solve your fundamental problem, rather than trying to work around it with an xmail configuration.

Regards,
Jobber
PMEmail Poster
Top
BizOdd
Posted: Mar 17 2009, 07:51 PM
Quote Post


Member
***

Group: Members
Posts: 58
Member No.: 1386
Joined: 1-November 04



Hi Jobber_Jobber
thanks for the reply.

Every machine ive run that query on
has come back with the same 'bad' answer.

I wonder if ive messed up some thing in the servers resolv.conf file?
for example my server called "mail.responsivetechnology.com"
has a resolv.conf file as follows:

domain responsivetechnology.com
nameserver 64.34.160.92
nameserver 64.34.160.76
options rotate

Anyone see a problem with that? those two name servers are the
hosting companies DNS servers.

Regards
BizOdd
PMEmail Poster
Top
jobber_jobber
Posted: Mar 18 2009, 02:38 AM
Quote Post


Newbie
*

Group: Members
Posts: 19
Member No.: 1307
Joined: 13-September 04



Hi,

One way of seeing whether it's the DNS servers or not, is to replace the entries in resolv.conf with say the DNS servers from opendns.


They are:

208.67.222.222
208.67.220.220

If you want more details go to http://www.opendns.com

Hope that helps,

jobber
PMEmail Poster
Top
BizOdd
Posted: Mar 18 2009, 03:41 PM
Quote Post


Member
***

Group: Members
Posts: 58
Member No.: 1386
Joined: 1-November 04



Hi Jobber_Jobber
I changed my resolv.conf
to only have those two OpenDns entries
then restarted XMail, and sent a test.

I got the same error again.
Can you try to send a test email to :
info@purvismarine.com
or
info@greatnorthernsnowcat.com
from your XMail server, and let me know if it works for you ?

thanks
-BizOdd


PMEmail Poster
Top
BizOdd
Posted: Mar 18 2009, 07:36 PM
Quote Post


Member
***

Group: Members
Posts: 58
Member No.: 1386
Joined: 1-November 04



Hi All,
So ive discovered the underlying issue:
both of those domains (purvismarine.com and greatnorthernsnowcat.com)
have 2 ns records. one that works, and one that does not.

I asked the xmail Mailinglist if there was any way to bypass XMail's DNS lookups
and Francis had the solution for me:

QUOTE

- Get greatnorthernsnowcat.com mx ip (current mx seems to be  mail.greatnorthernsnowcat.com, at ip 208.64.136.91)
- In xmail smtpfwd.tab file add a line like this :

"greatnorthernsnowcat.com"[TAB]"208.64.136.91:25"

That's all smile.gif



Worked like a charm.

Also, FYI: found the DNS info at: www.howismydns.com

-BizOdd
PMEmail Poster
Top
0 User(s) are reading this topic (0 Guests and 0 Anonymous Users)
0 Members:
« Next Oldest | XMail Server | Next Newest »

Reply to this topicStart new topicStart Poll