RE: DNS for wbpr.com
Why is it never *their* fault? :) I had the exact same issue and it took 2 months for me to convince them that they had to contact their ISP to make the change. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 4:17 PM To: Exchange Discussions Subject: RE: DNS for wbpr.com The preference can be anything from 0 to 65534 or so. 10 tends to be customary as primary, but it doesn't matter. The issue is indeed on their end - specifically their DNS entries. Your IMC is doing a lookup for ALL MX records for wbpr.com, and gets back just one - mail.wbpr.com. When it looks that up to find the IP address, its dealing with round robin DNS - you roll the dice and you take your chances. But, your DNS server will cache that value for a length of time (determined by their zone information). Generally that's >4 hours. Now - since your IMC will retry every 4 hours or so, because it's a transient error (can resolve via DNS but the server isn't available) - you're going to end up with that data live in the cache for a while... In other words. You lost the roll of the dice. The issue is their DNS and only their DNS. Roger -- Roger D. Seielstad - MCSE Sr. Systems Administrator Peregrine Systems Atlanta, GA > -Original Message- > From: Kevin Miller [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 15, 2002 4:08 PM > To: Exchange Discussions > Subject: RE: DNS for wbpr.com > > > DDNS hosted DNS with a multi homed server that is autoupdateing//?? > > Why is the cost 100?? Should be like 10. > > --Kevinm TSSSBE, M, WLKMMAS, UCC+WCA, And Beyond > http://www.daughtry.ca/ For Graphics and WebDesign, GO here! > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > Martin Blackstone > Sent: Monday, April 15, 2002 1:04 PM > To: Exchange Discussions > Subject: RE: DNS for wbpr.com > > > I see what you are talking about. > Mail.wbpr.com has 2 IP's. > > Strange > > Non-authoritative answer: > wbpr.comMX preference = 100, mail exchanger = mail.wbpr.com > > wbpr.comnameserver = nameserver.coqui.net > wbpr.comnameserver = nameserver.coqui.com > mail.wbpr.com internet address = 196.42.23.4 > mail.wbpr.com internet address = 64.213.243.212 > nameserver.coqui.netinternet address = 196.28.61.36 > nameserver.coqui.cominternet address = 196.28.61.66 > > -----Original Message- > From: Lynne July [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 15, 2002 12:58 PM > To: Exchange Discussions > Subject: DNS for wbpr.com > > > Our client, wbpr.com, appears to have issues with their DNS > records. They have 2 MX records with the same preference, and > one of the boxes > (64.213.243.212) does not respond. Of course, *my* DNS > server tries to connect to that one first, resulting in the > dreaded "Host Unreachable" error. The 2nd IP is never attempted. > > If I hard code the good IP (196.42.23.4) in the IMS, > magically the mail delivers. > > Of course, the customer claims no one else on earth is having > problems sending them mail. Obviously it's a DNS issue - but > is it *my* DNS server's fault that it never looks for the 2nd > IP address, or is it their problem? (dnsstuff.com couldn't > even connect to their mail server, so I'm voting for it's > their problem.) > > Many thanks. > > Lynne July > > _ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin:[EMAIL PROTECTED] > > _ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin:[EMAIL PROTECTED] > > > _ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin:[EMAIL PROTECTED] > _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: DNS for wbpr.com
The preference can be anything from 0 to 65534 or so. 10 tends to be customary as primary, but it doesn't matter. The issue is indeed on their end - specifically their DNS entries. Your IMC is doing a lookup for ALL MX records for wbpr.com, and gets back just one - mail.wbpr.com. When it looks that up to find the IP address, its dealing with round robin DNS - you roll the dice and you take your chances. But, your DNS server will cache that value for a length of time (determined by their zone information). Generally that's >4 hours. Now - since your IMC will retry every 4 hours or so, because it's a transient error (can resolve via DNS but the server isn't available) - you're going to end up with that data live in the cache for a while... In other words. You lost the roll of the dice. The issue is their DNS and only their DNS. Roger -- Roger D. Seielstad - MCSE Sr. Systems Administrator Peregrine Systems Atlanta, GA > -Original Message- > From: Kevin Miller [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 15, 2002 4:08 PM > To: Exchange Discussions > Subject: RE: DNS for wbpr.com > > > DDNS hosted DNS with a multi homed server that is autoupdateing//?? > > Why is the cost 100?? Should be like 10. > > --Kevinm TSSSBE, M, WLKMMAS, UCC+WCA, And Beyond > http://www.daughtry.ca/ For Graphics and WebDesign, GO here! > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > Martin Blackstone > Sent: Monday, April 15, 2002 1:04 PM > To: Exchange Discussions > Subject: RE: DNS for wbpr.com > > > I see what you are talking about. > Mail.wbpr.com has 2 IP's. > > Strange > > Non-authoritative answer: > wbpr.comMX preference = 100, mail exchanger = mail.wbpr.com > > wbpr.comnameserver = nameserver.coqui.net > wbpr.comnameserver = nameserver.coqui.com > mail.wbpr.com internet address = 196.42.23.4 > mail.wbpr.com internet address = 64.213.243.212 > nameserver.coqui.netinternet address = 196.28.61.36 > nameserver.coqui.cominternet address = 196.28.61.66 > > -----Original Message- > From: Lynne July [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 15, 2002 12:58 PM > To: Exchange Discussions > Subject: DNS for wbpr.com > > > Our client, wbpr.com, appears to have issues with their DNS > records. They have 2 MX records with the same preference, and > one of the boxes > (64.213.243.212) does not respond. Of course, *my* DNS > server tries to connect to that one first, resulting in the > dreaded "Host Unreachable" error. The 2nd IP is never attempted. > > If I hard code the good IP (196.42.23.4) in the IMS, > magically the mail delivers. > > Of course, the customer claims no one else on earth is having > problems sending them mail. Obviously it's a DNS issue - but > is it *my* DNS server's fault that it never looks for the 2nd > IP address, or is it their problem? (dnsstuff.com couldn't > even connect to their mail server, so I'm voting for it's > their problem.) > > Many thanks. > > Lynne July > > _ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin:[EMAIL PROTECTED] > > _ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin:[EMAIL PROTECTED] > > > _ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin:[EMAIL PROTECTED] > _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: DNS for wbpr.com
They actually have ONE MX record that points to a dual homed server [1]. The 64.213.243.212 address does not respond to port 25. If your server tries that one first and cannot get a response, it won't try the other IP, because that host is not responding. They need to clean up their DNS records that they publish to the Internet. Serdar Soysal [1] Of course, it could also be a weird attempt to expose more than one mail server to the Internet by unskilled gorillas, but I wanted to give them the benefit of the doubt. -Original Message- From: Lynne July [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 3:58 PM To: Exchange Discussions Subject: DNS for wbpr.com Our client, wbpr.com, appears to have issues with their DNS records. They have 2 MX records with the same preference, and one of the boxes (64.213.243.212) does not respond. Of course, *my* DNS server tries to connect to that one first, resulting in the dreaded "Host Unreachable" error. The 2nd IP is never attempted. If I hard code the good IP (196.42.23.4) in the IMS, magically the mail delivers. Of course, the customer claims no one else on earth is having problems sending them mail. Obviously it's a DNS issue - but is it *my* DNS server's fault that it never looks for the 2nd IP address, or is it their problem? (dnsstuff.com couldn't even connect to their mail server, so I'm voting for it's their problem.) Many thanks. Lynne July _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: DNS for wbpr.com
DDNS hosted DNS with a multi homed server that is autoupdateing//?? Why is the cost 100?? Should be like 10. --Kevinm TSSSBE, M, WLKMMAS, UCC+WCA, And Beyond http://www.daughtry.ca/ For Graphics and WebDesign, GO here! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Martin Blackstone Sent: Monday, April 15, 2002 1:04 PM To: Exchange Discussions Subject: RE: DNS for wbpr.com I see what you are talking about. Mail.wbpr.com has 2 IP's. Strange Non-authoritative answer: wbpr.comMX preference = 100, mail exchanger = mail.wbpr.com wbpr.comnameserver = nameserver.coqui.net wbpr.comnameserver = nameserver.coqui.com mail.wbpr.com internet address = 196.42.23.4 mail.wbpr.com internet address = 64.213.243.212 nameserver.coqui.netinternet address = 196.28.61.36 nameserver.coqui.cominternet address = 196.28.61.66 -Original Message- From: Lynne July [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:58 PM To: Exchange Discussions Subject: DNS for wbpr.com Our client, wbpr.com, appears to have issues with their DNS records. They have 2 MX records with the same preference, and one of the boxes (64.213.243.212) does not respond. Of course, *my* DNS server tries to connect to that one first, resulting in the dreaded "Host Unreachable" error. The 2nd IP is never attempted. If I hard code the good IP (196.42.23.4) in the IMS, magically the mail delivers. Of course, the customer claims no one else on earth is having problems sending them mail. Obviously it's a DNS issue - but is it *my* DNS server's fault that it never looks for the 2nd IP address, or is it their problem? (dnsstuff.com couldn't even connect to their mail server, so I'm voting for it's their problem.) Many thanks. Lynne July _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: DNS for wbpr.com
I see what you are talking about. Mail.wbpr.com has 2 IP's. Strange Non-authoritative answer: wbpr.comMX preference = 100, mail exchanger = mail.wbpr.com wbpr.comnameserver = nameserver.coqui.net wbpr.comnameserver = nameserver.coqui.com mail.wbpr.com internet address = 196.42.23.4 mail.wbpr.com internet address = 64.213.243.212 nameserver.coqui.netinternet address = 196.28.61.36 nameserver.coqui.cominternet address = 196.28.61.66 -Original Message- From: Lynne July [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:58 PM To: Exchange Discussions Subject: DNS for wbpr.com Our client, wbpr.com, appears to have issues with their DNS records. They have 2 MX records with the same preference, and one of the boxes (64.213.243.212) does not respond. Of course, *my* DNS server tries to connect to that one first, resulting in the dreaded "Host Unreachable" error. The 2nd IP is never attempted. If I hard code the good IP (196.42.23.4) in the IMS, magically the mail delivers. Of course, the customer claims no one else on earth is having problems sending them mail. Obviously it's a DNS issue - but is it *my* DNS server's fault that it never looks for the 2nd IP address, or is it their problem? (dnsstuff.com couldn't even connect to their mail server, so I'm voting for it's their problem.) Many thanks. Lynne July _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
DNS for wbpr.com
Our client, wbpr.com, appears to have issues with their DNS records. They have 2 MX records with the same preference, and one of the boxes (64.213.243.212) does not respond. Of course, *my* DNS server tries to connect to that one first, resulting in the dreaded "Host Unreachable" error. The 2nd IP is never attempted. If I hard code the good IP (196.42.23.4) in the IMS, magically the mail delivers. Of course, the customer claims no one else on earth is having problems sending them mail. Obviously it's a DNS issue - but is it *my* DNS server's fault that it never looks for the 2nd IP address, or is it their problem? (dnsstuff.com couldn't even connect to their mail server, so I'm voting for it's their problem.) Many thanks. Lynne July _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
