[xmail] Re: ENODNS Error
On 7 Apr 2007, at 20:08, Don Drake wrote: I don't get it. I just upgraded to 1.24 (more emails on that later), and I'm still getting ENODNS from @returns.bulk.yahoo.com. I just commented out my SmartDNSHost setting and cleared dnscache and it's still occurring. Now that I'm grasping for straws, the from email is quite large (it's 99 characters), would that matter? Just be clear, CheckMailerDomain checks that the 'MAIL FROM:' domain exists (MX or A record) and not the IP/name of the sender? -Don -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Saturday, April 07, 2007 1:39 PM To: xmail@xmailserver.org Subject: [xmail] Re: ENODNS Error On Sat, 7 Apr 2007, Don Drake wrote: Sure do: SmartDNSHost 10.1.0.15:tcp,216.86.146.9:udp Then you have to see MX queries, unless they're cached. The *only* way you get into the ENODNS error, if after XMail tried MX queries before and A record after. I normally have CheckMailerDomain disabled and just tried with MAIL FROM: [EMAIL PROTECTED] and it was accepted. Then enabled CheckMailerDomain and same MAIL FROM: is rejected with 505 Your domain has not DNS/MX entries This is 1.25-pre02. 'host returns.bulk.yahoo.com' gives list of six mx hosts, c1.bullet.mud.yahoo.com etc, and for each of those I see what appears to be an A record. Now I try MAIL FROM: [EMAIL PROTECTED] 250 OK Now I try MAIL FROM: [EMAIL PROTECTED] 250 OK Now I disable CheckMailerDomain again. So there is something odd about returns.bulk.yahoo.com. That's about my limit to working out dns issues. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
It looks like returns.bulk.yahoo.com has ONLY MX records, no A records... ; DiG 9.3.4 returns.bulk.yahoo.com IN A ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 33585 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;returns.bulk.yahoo.com.IN A ;; AUTHORITY SECTION: yahoo.com. 60 IN SOA ns1.yahoo.com. hostmaster.yahoo-inc.com. 2007040801 3600 300 1814400 600 ;; Query time: 34 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Apr 8 19:36:29 2007 ;; MSG SIZE rcvd: 101 - Original Message - From: David Lord [EMAIL PROTECTED] To: xmail@xmailserver.org Sent: Sunday, April 08, 2007 11:53 AM Subject: [xmail] Re: ENODNS Error On 7 Apr 2007, at 20:08, Don Drake wrote: I don't get it. I just upgraded to 1.24 (more emails on that later), and I'm still getting ENODNS from @returns.bulk.yahoo.com. I just commented out my SmartDNSHost setting and cleared dnscache and it's still occurring. Now that I'm grasping for straws, the from email is quite large (it's 99 characters), would that matter? Just be clear, CheckMailerDomain checks that the 'MAIL FROM:' domain exists (MX or A record) and not the IP/name of the sender? -Don -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Saturday, April 07, 2007 1:39 PM To: xmail@xmailserver.org Subject: [xmail] Re: ENODNS Error On Sat, 7 Apr 2007, Don Drake wrote: Sure do: SmartDNSHost 10.1.0.15:tcp,216.86.146.9:udp Then you have to see MX queries, unless they're cached. The *only* way you get into the ENODNS error, if after XMail tried MX queries before and A record after. I normally have CheckMailerDomain disabled and just tried with MAIL FROM: [EMAIL PROTECTED] and it was accepted. Then enabled CheckMailerDomain and same MAIL FROM: is rejected with 505 Your domain has not DNS/MX entries This is 1.25-pre02. 'host returns.bulk.yahoo.com' gives list of six mx hosts, c1.bullet.mud.yahoo.com etc, and for each of those I see what appears to be an A record. Now I try MAIL FROM: [EMAIL PROTECTED] 250 OK Now I try MAIL FROM: [EMAIL PROTECTED] 250 OK Now I disable CheckMailerDomain again. So there is something odd about returns.bulk.yahoo.com. That's about my limit to working out dns issues. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
I have the same ENODNS with xmail 1.21 Interestingly, dnsreport.com for returns.bulk.yahoo.com says: I was unable to get an answer from the parent servers [bulk.yahoo.com], when I tried to find the NS records for returns.bulk.yahoo.com. Could that be the problem? Dave - Original Message - From: Ivo Smits [EMAIL PROTECTED] To: xmail@xmailserver.org Sent: Sunday, April 08, 2007 6:36 PM Subject: [xmail] Re: ENODNS Error It looks like returns.bulk.yahoo.com has ONLY MX records, no A records... ; DiG 9.3.4 returns.bulk.yahoo.com IN A ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 33585 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;returns.bulk.yahoo.com.IN A ;; AUTHORITY SECTION: yahoo.com. 60 IN SOA ns1.yahoo.com. hostmaster.yahoo-inc.com. 2007040801 3600 300 1814400 600 ;; Query time: 34 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Apr 8 19:36:29 2007 ;; MSG SIZE rcvd: 101 - Original Message - From: David Lord [EMAIL PROTECTED] To: xmail@xmailserver.org Sent: Sunday, April 08, 2007 11:53 AM Subject: [xmail] Re: ENODNS Error On 7 Apr 2007, at 20:08, Don Drake wrote: I don't get it. I just upgraded to 1.24 (more emails on that later), and I'm still getting ENODNS from @returns.bulk.yahoo.com. I just commented out my SmartDNSHost setting and cleared dnscache and it's still occurring. Now that I'm grasping for straws, the from email is quite large (it's 99 characters), would that matter? Just be clear, CheckMailerDomain checks that the 'MAIL FROM:' domain exists (MX or A record) and not the IP/name of the sender? -Don -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Saturday, April 07, 2007 1:39 PM To: xmail@xmailserver.org Subject: [xmail] Re: ENODNS Error On Sat, 7 Apr 2007, Don Drake wrote: Sure do: SmartDNSHost 10.1.0.15:tcp,216.86.146.9:udp Then you have to see MX queries, unless they're cached. The *only* way you get into the ENODNS error, if after XMail tried MX queries before and A record after. I normally have CheckMailerDomain disabled and just tried with MAIL FROM: [EMAIL PROTECTED] and it was accepted. Then enabled CheckMailerDomain and same MAIL FROM: is rejected with 505 Your domain has not DNS/MX entries This is 1.25-pre02. 'host returns.bulk.yahoo.com' gives list of six mx hosts, c1.bullet.mud.yahoo.com etc, and for each of those I see what appears to be an A record. Now I try MAIL FROM: [EMAIL PROTECTED] 250 OK Now I try MAIL FROM: [EMAIL PROTECTED] 250 OK Now I disable CheckMailerDomain again. So there is something odd about returns.bulk.yahoo.com. That's about my limit to working out dns issues. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
On Sun, 8 Apr 2007, Dave Taylor wrote: I have the same ENODNS with xmail 1.21 Interestingly, dnsreport.com for returns.bulk.yahoo.com says: I was unable to get an answer from the parent servers [bulk.yahoo.com], when I tried to find the NS records for returns.bulk.yahoo.com. Could that be the problem? Probably a broken DNS: http://www.dnsreport.com/tools/dnsreport.ch?domain=returns.bulk.yahoo.com. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
On Sun, 8 Apr 2007, Davide Libenzi wrote: On Sun, 8 Apr 2007, Dave Taylor wrote: I have the same ENODNS with xmail 1.21 Interestingly, dnsreport.com for returns.bulk.yahoo.com says: I was unable to get an answer from the parent servers [bulk.yahoo.com], when I tried to find the NS records for returns.bulk.yahoo.com. Could that be the problem? Probably a broken DNS: http://www.dnsreport.com/tools/dnsreport.ch?domain=returns.bulk.yahoo.com. OTOH, `dig` fetch MX just fine: [EMAIL PROTECTED]:~$ dig returns.bulk.yahoo.com. mx +trace ; DiG 9.3.4 returns.bulk.yahoo.com. mx +trace ;; global options: printcmd .. 9713IN NS a.root-servers.net. .. 9713IN NS b.root-servers.net. .. 9713IN NS c.root-servers.net. .. 9713IN NS d.root-servers.net. .. 9713IN NS e.root-servers.net. .. 9713IN NS f.root-servers.net. .. 9713IN NS g.root-servers.net. .. 9713IN NS h.root-servers.net. .. 9713IN NS i.root-servers.net. .. 9713IN NS j.root-servers.net. .. 9713IN NS k.root-servers.net. .. 9713IN NS l.root-servers.net. .. 9713IN NS m.root-servers.net. ;; Received 292 bytes from 10.107.17.218#53(10.107.17.218) in 0 ms 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. 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. ;; Received 512 bytes from 198.41.0.4#53(a.root-servers.net) in 88 ms yahoo.com. 172800 IN NS ns1.yahoo.com. yahoo.com. 172800 IN NS ns2.yahoo.com. yahoo.com. 172800 IN NS ns3.yahoo.com. yahoo.com. 172800 IN NS ns4.yahoo.com. yahoo.com. 172800 IN NS ns5.yahoo.com. ;; Received 210 bytes from 192.54.112.30#53(H.GTLD-SERVERS.NET) in 179 ms returns.bulk.yahoo.com. 1800IN MX 1 c3.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c4.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c5.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c6.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c1.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c2.bullet.mud.yahoo.com. yahoo.com. 172800 IN NS ns2.yahoo.com. yahoo.com. 172800 IN NS ns1.yahoo.com. yahoo.com. 172800 IN NS ns3.yahoo.com. yahoo.com. 172800 IN NS ns4.yahoo.com. yahoo.com. 172800 IN NS ns5.yahoo.com. yahoo.com. 172800 IN NS ns8.yahoo.com. yahoo.com. 172800 IN NS ns9.yahoo.com. ;; Received 499 bytes from 66.218.71.63#53(ns1.yahoo.com) in 26 ms - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
It SHOULD check at the nameservers for yahoo.com, if they return the requested record (MX), the resolver has its answer (which is the case!), if it does not return the requested record type, it should retry at the returned NS records. The DNS IS NOT broken.Sorry, Davide, it really looks like a bug in your code to me ;) I think that your resolver is trying to fetch the NS records for c2.bullet.mud.yahoo.com, which do not exist, and fails, while it should just use the NS records of yahoo.com. Isn't there a way to just use a system resolver function, instead of your own recursive resolver? To see what *should be* going on, try: dig returns.bulk.yahoo.com IN MX +trace ns1.yahoo.com returns: returns.bulk.yahoo.com. 1800IN MX 1 c2.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c3.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c4.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c5.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c6.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c1.bullet.mud.yahoo.com. yahoo.com. 172800 IN NS ns2.yahoo.com. yahoo.com. 172800 IN NS ns1.yahoo.com. yahoo.com. 172800 IN NS ns3.yahoo.com. yahoo.com. 172800 IN NS ns4.yahoo.com. yahoo.com. 172800 IN NS ns5.yahoo.com. yahoo.com. 172800 IN NS ns8.yahoo.com. yahoo.com. 172800 IN NS ns9.yahoo.com. ;; Received 499 bytes from 66.218.71.63#53(ns1.yahoo.com) in 202 ms - Original Message - From: Davide Libenzi davidel@xmailserver.org To: xmail@xmailserver.org Sent: Sunday, April 08, 2007 10:09 PM Subject: [xmail] Re: ENODNS Error On Sun, 8 Apr 2007, Dave Taylor wrote: I have the same ENODNS with xmail 1.21 Interestingly, dnsreport.com for returns.bulk.yahoo.com says: I was unable to get an answer from the parent servers [bulk.yahoo.com], when I tried to find the NS records for returns.bulk.yahoo.com. Could that be the problem? Probably a broken DNS: http://www.dnsreport.com/tools/dnsreport.ch?domain=returns.bulk.yahoo.com. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
On Sun, 8 Apr 2007, Ivo Smits wrote: It SHOULD check at the nameservers for yahoo.com, if they return the requested record (MX), the resolver has its answer (which is the case!), if it does not return the requested record type, it should retry at the returned NS records. It does. It tries to go the deeper as possible in the NS hierarchy, then issues the query. I'll try to debug, even if the fact that dnsreport reports broken DNS should be an hint. The DNS IS NOT broken.Sorry, Davide, it really looks like a bug in your code to me ;) What are you talking about?!? Don't you know my code does not have bugs?!? :) I think that your resolver is trying to fetch the NS records for c2.bullet.mud.yahoo.com, which do not exist, and fails, while it should just use the NS records of yahoo.com. Isn't there a way to just use a system resolver function, instead of your own recursive resolver? SmartDNSHost - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
On Sun, 8 Apr 2007, Davide Libenzi wrote: On Sun, 8 Apr 2007, Ivo Smits wrote: It SHOULD check at the nameservers for yahoo.com, if they return the requested record (MX), the resolver has its answer (which is the case!), if it does not return the requested record type, it should retry at the returned NS records. It does. It tries to go the deeper as possible in the NS hierarchy, then issues the query. I'll try to debug, even if the fact that dnsreport reports broken DNS should be an hint. That seems really screwed: - A query for returns.bulk.yahoo.com. NS returns an SOA record pointing to @ns1.yahoo.com. - A query for returns.bulk.yahoo.com. NS at @ns1.yahoo.com. returns returns.bulk.yahoo.com. being a CNAME for mailer1.bulk.scd.yahoo.com. - A query for mailer1.bulk.scd.yahoo.com. NS at @ns1.yahoo.com. returns mailer1.bulk.scd.yahoo.com. being a CNAME for t1.bullet.scd.yahoo.com. - A query for t1.bullet.scd.yahoo.com. MX return a broken record [EMAIL PROTECTED]:~$ dig t1.bullet.scd.yahoo.com. mx ; DiG 9.3.4 t1.bullet.scd.yahoo.com. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 28320 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 7, ADDITIONAL: 7 ;; QUESTION SECTION: ;t1.bullet.scd.yahoo.com. IN MX ;; ANSWER SECTION: t1.bullet.scd.yahoo.com. 1800 IN MX 0 . - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
Davide Libenzi wrote: It SHOULD check at the nameservers for yahoo.com, if they return the requested record (MX), the resolver has its answer (which is the case!), if it does not return the requested record type, it should retry at the returned NS records. It does. It tries to go the deeper as possible in the NS hierarchy, then issues the query. I'll try to debug, even if the fact that dnsreport reports broken DNS should be an hint. That seems really screwed: - A query for returns.bulk.yahoo.com. NS returns an SOA record pointing to @ns1.yahoo.com. - A query for returns.bulk.yahoo.com. NS at @ns1.yahoo.com. returns returns.bulk.yahoo.com. being a CNAME for mailer1.bulk.scd.yahoo.com. - A query for mailer1.bulk.scd.yahoo.com. NS at @ns1.yahoo.com. returns mailer1.bulk.scd.yahoo.com. being a CNAME for t1.bullet.scd.yahoo.com. - A query for t1.bullet.scd.yahoo.com. MX return a broken record [EMAIL PROTECTED]:~$ dig t1.bullet.scd.yahoo.com. mx ; DiG 9.3.4 t1.bullet.scd.yahoo.com. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 28320 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 7, ADDITIONAL: 7 ;; QUESTION SECTION: ;t1.bullet.scd.yahoo.com. IN MX ;; ANSWER SECTION: t1.bullet.scd.yahoo.com. 1800 IN MX 0 . But interestingly enough, querying from here for an MX record for returns.bulk.yahoo.com, starting at the root and working forward, seems to return different records than what you found, even though the query ended up at the same nameserver as the one you queried E:\Digdig +recursive +trace +fail @h.root-servers.net returns.bulk.yahoo.com -t mx ; DiG 9.2.2 +recursive +trace +fail @h.root-servers.net returns.bulk.yahoo.com -t mx ;; global options: printcmd .. 518400 IN NS a.root-servers.net. .. 518400 IN NS b.root-servers.net. .. 518400 IN NS c.root-servers.net. .. 518400 IN NS d.root-servers.net. .. 518400 IN NS e.root-servers.net. .. 518400 IN NS f.root-servers.net. .. 518400 IN NS g.root-servers.net. .. 518400 IN NS h.root-servers.net. .. 518400 IN NS i.root-servers.net. .. 518400 IN NS j.root-servers.net. .. 518400 IN NS k.root-servers.net. .. 518400 IN NS l.root-servers.net. .. 518400 IN NS m.root-servers.net. ;; Received 436 bytes from 128.63.2.53#53(h.root-servers.net) in 160 ms 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. 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. ;; Received 512 bytes from 198.41.0.4#53(a.root-servers.net) in 100 ms yahoo.com. 172800 IN NS ns1.yahoo.com. yahoo.com. 172800 IN NS ns2.yahoo.com. yahoo.com. 172800 IN NS ns3.yahoo.com. yahoo.com. 172800 IN NS ns4.yahoo.com. yahoo.com. 172800 IN NS ns5.yahoo.com. ;; Received 210 bytes from 192.41.162.30#53(L.GTLD-SERVERS.NET) in 160 ms returns.bulk.yahoo.com. 1800IN MX 1 c5.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c6.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c1.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c2.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c3.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c4.bullet.mud.yahoo.com. yahoo.com. 172800 IN NS ns2.yahoo.com. yahoo.com. 172800 IN NS ns1.yahoo.com. yahoo.com. 172800 IN NS ns3.yahoo.com. yahoo.com. 172800 IN NS ns4.yahoo.com. yahoo.com. 172800 IN NS ns5.yahoo.com. yahoo.com. 172800 IN NS ns8.yahoo.com.
[xmail] Another dns query - xmailserver.org.blackhole.securitysage.com
I've just noticed named is throwing up an error each time a connection is made from xmailserver.org. unexpected RCODE (SERVFAIL) resolving 'xmailserver.org.blackhole.securitysage.com/A/IN' Looking back through logs I see this started on April 4. Any ideas what this is due to? I'll try to work out what changes I made recently but guess it's from my isps nameserver as start of problem coincides with problem there. I've restarted xmail just in case. David - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: ENODNS Error
Ivo, I totally agree with your method. What is strange is that even with SmartDNSHost enabled with servers that can recurse, I still have this problem, which to me means there might be a problem with the Xmail code. Davide, the buck stops with you, what is your opinion? Thanks. -Don -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ivo Smits Sent: Sunday, April 08, 2007 5:10 PM To: xmail@xmailserver.org Subject: [xmail] Re: ENODNS Error Holy.. whatever... When issuing a query for an A record, it indeed ONLY returns the SOA record, which is invalid (it should return the NS record..) When issuing a query for a MX recors, it returns some MX records AND the NS records (no SOA, but we didnt ask for that one): returns.bulk.yahoo.com. 1800IN MX 1 c5.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c6.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c1.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c2.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c3.bullet.mud.yahoo.com. returns.bulk.yahoo.com. 1800IN MX 1 c4.bullet.mud.yahoo.com. yahoo.com. 172800 IN NS ns2.yahoo.com. yahoo.com. 172800 IN NS ns1.yahoo.com. yahoo.com. 172800 IN NS ns3.yahoo.com. yahoo.com. 172800 IN NS ns4.yahoo.com. yahoo.com. 172800 IN NS ns5.yahoo.com. yahoo.com. 172800 IN NS ns8.yahoo.com. yahoo.com. 172800 IN NS ns9.yahoo.com. ;; Received 499 bytes from 66.218.71.63#53(ns1.yahoo.com) in 173 ms Your resolver should (recursively) try nameservers until it has its answer, so if it gets the answer to the MX query from the yahoo.com nameserver, it should use that one and forget about any lower levels, like dig does. This also helps when using a (decent) recursor. You could even use the same routine for the smartdnshost! :p By the way, I just found out that my Speedtouch router/modem/NAT/dns/whatever can ONLY return A records, NO NS or MX records :'( - Original Message - From: Davide Libenzi davidel@xmailserver.org To: xmail@xmailserver.org Sent: Sunday, April 08, 2007 11:43 PM Subject: [xmail] Re: ENODNS Error On Sun, 8 Apr 2007, Davide Libenzi wrote: On Sun, 8 Apr 2007, Ivo Smits wrote: It SHOULD check at the nameservers for yahoo.com, if they return the requested record (MX), the resolver has its answer (which is the case!), if it does not return the requested record type, it should retry at the returned NS records. It does. It tries to go the deeper as possible in the NS hierarchy, then issues the query. I'll try to debug, even if the fact that dnsreport reports broken DNS should be an hint. That seems really screwed: - A query for returns.bulk.yahoo.com. NS returns an SOA record pointing to @ns1.yahoo.com. - A query for returns.bulk.yahoo.com. NS at @ns1.yahoo.com. returns returns.bulk.yahoo.com. being a CNAME for mailer1.bulk.scd.yahoo.com. - A query for mailer1.bulk.scd.yahoo.com. NS at @ns1.yahoo.com. returns mailer1.bulk.scd.yahoo.com. being a CNAME for t1.bullet.scd.yahoo.com. - A query for t1.bullet.scd.yahoo.com. MX return a broken record [EMAIL PROTECTED]:~$ dig t1.bullet.scd.yahoo.com. mx ; DiG 9.3.4 t1.bullet.scd.yahoo.com. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 28320 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 7, ADDITIONAL: 7 ;; QUESTION SECTION: ;t1.bullet.scd.yahoo.com. IN MX ;; ANSWER SECTION: t1.bullet.scd.yahoo.com. 1800 IN MX 0 . - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Another dns query - xmailserver.org.blackhole.securitysage.com
On 8 Apr 2007, at 23:09, David Lord wrote: I've just noticed named is throwing up an error each time a connection is made from xmailserver.org. unexpected RCODE (SERVFAIL) resolving 'xmailserver.org.blackhole.securitysage.com/A/IN' Looking back through logs I see this started on April 4. Any ideas what this is due to? I'll try to work out what changes I made recently but guess it's from my isps nameserver as start of problem coincides with problem there. I've restarted xmail just in case. A google indicated it was from a blocking list that's now offline. I use spamassassin and that is one of the lists it was configured to use. Sorry for the noise. David - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
