Good Morning, List; We've got a problem that is driving both me and our client crazy. Their domain CHICAGOHOUSE.ORG cannot receive e-mail from certain other two or three domains. The only indication of any problem is a NO GLUE item in the DNSREPORT we ran.
We're running iMail 8.0 with the first patch applied on a Windows 2000 Server, 1 meg of memory, mirrored hard drives. iMail is on its own partition. The domains having the most problems sending e-mail to CHICAGOHOUSE.ORG are: WORK-PLACES.COM and DESMONDCPA.COM. We've checked all of the DNS entries, added two additional DNS servers that are not on the same sub-net as ours, incremented the date in the DNS record in hopes of forcing the servers at Network Solutions to rebuild the record and checked every machine we can possible think might have something to do with this - both on our end and at the client's three locations. We have nothing in the "kill list" that would preclude the domains in question from send mail to them. We have no log entries in our logs from these domains indicating that they have ever connected to our server. We've even disabled the firewall while we attempt to resolve this. Below are the various tests and messages we've searched while attempting to resolve this problem. Any assistance that can be offered by anyone on this list will be greatly appreciated. Bruce Barnes ChicagoNetTech Inc [EMAIL PROTECTED] Office: 773.365.0105 X221 Outside Chicago: 800.982.0839 Cell: 773.491.9019 Here's the error message from the sending server - as forwarded via another e-mail address: -------- Original Message -------- Subject: Delivery Status Notification Date: 23 Jul 2003 13:01:58 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] This message could not be delivered to the following recipients: :Connected to 65.86.164.132 but greeting failed. I'm not going to try again; this message has been in the queue too long. :Connected to 65.86.164.132 but greeting failed. I'm not going to try again; this message has been in the queue too long. Here is the error message: Reporting-MTA: dns; bouncemessage.net Final-Recipient: rfc822; [EMAIL PROTECTED] Action: Failed Status: 5.0.0 When we checked the spam databases for the IP address of 65.86.164.132, (http://www.dnsstuff.com/tools/ip4r.ch?ip=65.86.164.132) the address of the server, there are no listings reported for the address. When we do a DNSREPORT on CHICAGOHOUSE.ORG, (http://www.dnsreport.com/tools/dnsreport.ch?domain=chicagohouse.org) we are told there is "no glue". INFO - NS records at parent servers Your NS records at the parent servers are: NS10.RIZNET.NET. [65.86.164.141 (NO GLUE)] NS1.CHICAGONETTECH.COM. [65.86.164.133 (NO GLUE)] NS19.ZONEEDIT.COM. [69.10.134.196 (NO GLUE)] NS18.ZONEEDIT.COM. [65.125.227.35 (NO GLUE)] [These were obtained from a7.nstld.com] Glue at parent nameservers - WARNING. The parent servers (A7.NSTLD.COM.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause some incompatibilities with some programs (if the programs are not fully RFC-compliant). This behavior is allowed by the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.co.uk" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain. We are also told that the DNS servers are on the sane CLASS C (probably because NO GLUE) WARN - Nameservers on separate class C's WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location. [If the parent servers have no glue for your domain, this could be a false positive.] Here's what NSLOOKUP shows: > set type=all > chicagohouse.org Server: ns1.chicagonettech.com Address: 65.86.164.133 chicagohouse.org nameserver = ns1.chicagonettech.com chicagohouse.org nameserver = ns10.riznet.net chicagohouse.org nameserver = ns19.zoneedit.com chicagohouse.org nameserver = ns18.zoneedit.com chicagohouse.org primary name server = ns1.chicagonettech.com responsible mail addr = admin.chicagonettech.com serial = 2003082807 refresh = 7200 (2 hours) retry = 7200 (2 hours) expire = 604800 (7 days) default TTL = 3600 (1 hour) chicagohouse.org MX preference = 10, mail exchanger = mail.chicagohouse.org ns1.chicagonettech.com internet address = 65.86.164.133 ns10.riznet.net internet address = 65.86.164.141 mail.chicagohouse.org internet address = 65.86.164.132 > Here's our own ChicagoNetTech.com NSLOOKUP entry: > chicagonettech.com Server: ns1.chicagonettech.com Address: 65.86.164.133 chicagonettech.com internet address = 65.86.164.130 chicagonettech.com nameserver = ns1.chicagonettech.com chicagonettech.com nameserver = ns10.riznet.net chicagonettech.com nameserver = ns1.zoneedit.com chicagonettech.com nameserver = ns3.zoneedit.com chicagonettech.com primary name server = ns1.chicagonettech.com responsible mail addr = administrator.chicagonettech.com serial = 2003022310 refresh = 7200 (2 hours) retry = 7200 (2 hours) expire = 604800 (7 days) default TTL = 3600 (1 hour) chicagonettech.com MX preference = 10, mail exchanger = mail.chicagonettech.com chicagonettech.com WINS lookup flags = 0 ( ) lookup timeout = 2 cache TTL = 900 server count = 1 WINS server = (65.86.164.130) ns1.chicagonettech.com internet address = 65.86.164.133 ns10.riznet.net internet address = 65.86.164.141 mail.chicagonettech.com internet address = 65.86.164.132 Here's the NSLOOKUP for DESMONDCPA.COM: > desmondcpa.com Server: ns1.chicagonettech.com Address: 65.86.164.133 Non-authoritative answer: desmondcpa.com internet address = 205.178.180.170 desmondcpa.com nameserver = ns1.dsl.net desmondcpa.com nameserver = ns2.dsl.net desmondcpa.com primary name server = ns1.dsl.net responsible mail addr = domreg.dsl.net serial = 2001081000 refresh = 7200 (2 hours) retry = 3600 (1 hour) expire = 604800 (7 days) default TTL = 600 (10 mins) desmondcpa.com MX preference = 900, mail exchanger = mxr01.hvn01.dsl.net desmondcpa.com MX preference = 900, mail exchanger = mxr01.nyc01.dsl.net desmondcpa.com MX preference = 10, mail exchanger = inbound.desmondcpa.com.criticalpath.net ns1.dsl.net internet address = 209.87.64.70 ns2.dsl.net internet address = 209.87.79.232 mxr01.hvn01.dsl.net internet address = 209.87.64.79 mxr01.nyc01.dsl.net internet address = 209.87.79.229 > Here's the NSLOOKUP for WORK-PLACES.COM: > work-places.com Server: ns1.chicagonettech.com Address: 65.86.164.133 Non-authoritative answer: work-places.com internet address = 66.80.235.141 work-places.com nameserver = ns1.directnic.com work-places.com nameserver = ns0.directnic.com work-places.com primary name server = ns0.directnic.com responsible mail addr = hostmaster.directnic.com serial = 1050797539 refresh = 16384 (4 hours 33 mins 4 secs) retry = 2048 (34 mins 8 secs) expire = 1048576 (12 days 3 hours 16 mins 16 secs) default TTL = 2560 (42 mins 40 secs) work-places.com MX preference = 30, mail exchanger = mail2.work-places.com work-places.com MX preference = 25, mail exchanger = mail.work-places.com ns1.directnic.com internet address = 206.251.177.2 ns0.directnic.com internet address = 204.251.10.100 mail2.work-places.com internet address = 66.80.235.151 mail.work-places.com internet address = 66.80.235.150 > Here's an error reported on DNSREPORTS for WORK-PLACES.COM (http://www.dnsreport.com/tools/dnsreport.ch?domain=workplaces.com): FAIL - Connect to mail servers ERROR: I could not connect to one or more of your mailservers: mail2.work-places.com: Timed out [Last data sent: QUIT ] Finally, the mailserver returning the error message in the message that was included shows no problems in DNSREPORTS (http://www.dnsreport.com/tools/dnsreport.ch?domain=bouncemessage.net+) Here's their NSLOOKUP report: > bouncemessage.net Server: ns1.chicagonettech.com Address: 65.86.164.133 Non-authoritative answer: bouncemessage.net nameserver = ns1.cp.net bouncemessage.net nameserver = ns3.cp.net bouncemessage.net nameserver = ns1.cp.net bouncemessage.net nameserver = ns3.cp.net ns1.cp.net internet address = 209.228.15.4 ns3.cp.net internet address = 209.228.14.4 > > bouncemessage.net Server: ns1.chicagonettech.com Address: 65.86.164.133 bouncemessage.net primary name server = ns1.cp.net responsible mail addr = hostmaster.cp.net serial = 1999072000 refresh = 3600 (1 hour) retry = 1800 (30 mins) expire = 2419200 (28 days) default TTL = 3600 (1 hour) bouncemessage.net nameserver = ns1.cp.net bouncemessage.net nameserver = ns3.cp.net bouncemessage.net MX preference = 0, mail exchanger = inbound.bouncemessag e.net.criticalpath.net ns1.cp.net internet address = 209.228.15.4 ns3.cp.net internet address = 209.228.14.4 inbound.bouncemessage.net.criticalpath.net internet address = 209.228.4.171 To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
