Can someone who looks after Xtra's mail systems please contact me. We're seeing problems with Xtra customers delivering mail to a domain recently transferred from Xtra to DTS. It looks like there are some legacy records left behind from the removal process. Regards Tim Price Network Operations Manager DTS Limited.
This happens all the time - especially withTelecom Business Hub. We've found we have to call each time and explicitly ask to have them remove records.
Karl
On 17/10/2012, at 5:51 PM, "Tim Price"
Can someone who looks after Xtra’s mail systems please contact me. We’re seeing problems with Xtra customers delivering mail to a domain recently transferred from Xtra to DTS. It looks like there are some legacy records left behind from the removal process.
Regards
Tim Price Network Operations Manager DTS Limited. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Yeah when you move away from them they need to manually remove them after you have transferred it, they also won't remove billing even if the transfers fully completed - we've been stung a few times
Shane Langley
On 17/10/2012, at 6:02 PM, Karl Hardisty
This happens all the time - especially withTelecom Business Hub. We've found we have to call each time and explicitly ask to have them remove records.
Karl
On 17/10/2012, at 5:51 PM, "Tim Price"
wrote: Can someone who looks after Xtra’s mail systems please contact me. We’re seeing problems with Xtra customers delivering mail to a domain recently transferred from Xtra to DTS. It looks like there are some legacy records left behind from the removal process.
Regards
Tim Price Network Operations Manager DTS Limited. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
In theory it's up to the owner of the domain to notify Xtra that they no longer wish the service and to cancel the services tied to the domain (and without this, mail delivery obeys local configuration, not the DNS). Many years ago it was their opinion that they would not remove legacy email configuration without the explicit OK of the person who pays the bill - regardless of the DNS, MX records, Registry or impact to their other customers. But yes, a strange sense of deja-vu when I read this... My advice is ring 0800 BUSINESS and find the IVR options for Domain Names technical support - the group behind that line (CTS) are the most clooful of their front-end technical support staff. Even then lately i've found it's hit-and-miss, the calibre of the calltaker very much dictates your success (or not). Also, if you have customers transitioning to you from Xtra, make sure you strongly advise them to personally ensure that their Xtra service is cancelled promptly, and explain to them the risk to their email service if they don't... Mark. On 17/10/12 18:06, Shane Langley wrote:
Yeah when you move away from them they need to manually remove them after you have transferred it, they also won't remove billing even if the transfers fully completed - we've been stung a few times
Shane Langley
On 17/10/2012, at 6:02 PM, Karl Hardisty
mailto:karl(a)mothership.co.nz> wrote: This happens all the time - especially withTelecom Business Hub. We've found we have to call each time and explicitly ask to have them remove records.
Karl
On 17/10/2012, at 5:51 PM, "Tim Price"
mailto:tim(a)dts.net.nz> wrote: Can someone who looks after Xtra's mail systems please contact me. We're seeing problems with Xtra customers delivering mail to a domain recently transferred from Xtra to DTS. It looks like there are some legacy records left behind from the removal process.
Regards
If they properly separated their authoritative name service from their caching forwarders, this wouldn't be a problem. The change in delegation would mean nobody ever saw the old records ever again after the TTLs expired. This has been "best practice" since the late '90s, FFS. -- don On 17/10/12 18:39, Mark Foster wrote:
In theory it's up to the owner of the domain to notify Xtra that they no longer wish the service and to cancel the services tied to the domain (and without this, mail delivery obeys local configuration, not the DNS).
Many years ago it was their opinion that they would not remove legacy email configuration without the explicit OK of the person who pays the bill - regardless of the DNS, MX records, Registry or impact to their other customers.
But yes, a strange sense of deja-vu when I read this...
My advice is ring 0800 BUSINESS and find the IVR options for Domain Names technical support - the group behind that line (CTS) are the most clooful of their front-end technical support staff. Even then lately i've found it's hit-and-miss, the calibre of the calltaker very much dictates your success (or not).
Also, if you have customers transitioning to you from Xtra, make sure you strongly advise them to personally ensure that their Xtra service is cancelled promptly, and explain to them the risk to their email service if they don't...
Mark.
On 17/10/12 18:06, Shane Langley wrote:
Yeah when you move away from them they need to manually remove them after you have transferred it, they also won't remove billing even if the transfers fully completed - we've been stung a few times
Shane Langley
On 17/10/2012, at 6:02 PM, Karl Hardisty
mailto:karl(a)mothership.co.nz> wrote: This happens all the time - especially withTelecom Business Hub. We've found we have to call each time and explicitly ask to have them remove records.
Karl
On 17/10/2012, at 5:51 PM, "Tim Price"
mailto:tim(a)dts.net.nz> wrote: Can someone who looks after Xtra’s mail systems please contact me. We’re seeing problems with Xtra customers delivering mail to a domain recently transferred from Xtra to DTS. It looks like there are some legacy records left behind from the removal process.
Regards
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Is it possible that their MTA's configuration treating the domain as valid for local-delivery would mean the problem is still experienced by users who relay their outbound through said MTA, regardless of the state of DNS?
Pete Mundy
On 17/10/2012, at 6:47 PM, Don Stokes
If they properly separated their authoritative name service from their caching forwarders, this wouldn't be a problem. The change in delegation would mean nobody ever saw the old records ever again after the TTLs expired.
This has been "best practice" since the late '90s, FFS.
-- don
Based on symptoms that is exactly the case.
-----Original Message-----
From: nznog-bounces(a)list.waikato.ac.nz
[mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Pete Mundy
Sent: Wednesday, 17 October 2012 6:51 p.m.
To: NZNOG(a)list.waikato.ac.nz
Subject: Re: [nznog] Xtra mail admins around?
Is it possible that their MTA's configuration treating the domain as valid
for local-delivery would mean the problem is still experienced by users who
relay their outbound through said MTA, regardless of the state of DNS?
Pete Mundy
On 17/10/2012, at 6:47 PM, Don Stokes
If they properly separated their authoritative name service from their caching forwarders, this wouldn't be a problem. The change in delegation would mean nobody ever saw the old records ever again after the TTLs expired.
This has been "best practice" since the late '90s, FFS.
-- don
Pete's on the money.
On 17/10/2012, at 6:55 PM, "Tim Price"
Based on symptoms that is exactly the case.
-----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Pete Mundy Sent: Wednesday, 17 October 2012 6:51 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] Xtra mail admins around?
Is it possible that their MTA's configuration treating the domain as valid for local-delivery would mean the problem is still experienced by users who relay their outbound through said MTA, regardless of the state of DNS?
Pete Mundy
On 17/10/2012, at 6:47 PM, Don Stokes
wrote: If they properly separated their authoritative name service from their caching forwarders, this wouldn't be a problem. The change in delegation would mean nobody ever saw the old records ever again after the TTLs expired.
This has been "best practice" since the late '90s, FFS.
-- don
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
On Wed, 17 Oct 2012, Don Stokes wrote:
If they properly separated their authoritative name service from their caching forwarders, this wouldn't be a problem. The change in delegation would mean nobody ever saw the old records ever again after the TTLs expired.
This has been "best practice" since the late '90s, FFS.
Last discussed 6 months ago... http://list.waikato.ac.nz/pipermail/nznog/2012-March/018981.html -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.
On 18/10/12 13:54, Simon Lyall wrote:
On Wed, 17 Oct 2012, Don Stokes wrote:
If they properly separated their authoritative name service from their caching forwarders, this wouldn't be a problem.
Last discussed 6 months ago...
http://list.waikato.ac.nz/pipermail/nznog/2012-March/018981.html
Yep, and if they're still doing it, they're still clueless fracking idiots. The same principle actually applies to mail servers too (assuming Pete Mundy's assessment of the problem is correct, which is highly likely). You should have separate inbound and outbound mail servers. The inbound servers should handle all mail (and filter it) and only handle mail from random outside senders to known internal users (no relaying of any sort except as explicitly configured). The outbound servers should be the opposite; they relay mail from known internal users only, deal with local abuse (a different problem set to handling external abuse), and have no knowledge whatsoever about the destinations. They "ask the Internet." No "short-cutting" between the outbound service and the inbound service. If you do that, stale configuration stops being a (major) problem. A bunch of other problems (especially around abuse filtering) go away too. -- don
On Thu, 18 Oct 2012, Don Stokes wrote:
Yep, and if they're still doing it, they're still clueless fracking idiots.
Thankyou Don. I'm sure a bunch of people at Telecom have been wondering for years why their DNS and mail system didn't work and are now really grateful that you have pointed out the problem. I'm sure they will be jumping right at it to fix this little thing and it'll be done within the next few days. As we speak the share price has jumped 50 cents in anticipation of the huge increase in income the company will be seeing in the future once these fixes go though. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.
On 18/10/12 14:51, Simon Lyall wrote:
Thankyou Don. I'm sure a bunch of people at Telecom have been wondering for years why their DNS and mail system didn't work and are now really grateful that you have pointed out the problem.
And we all know that best current practice is just wank fodder for people that don't run DNS or mail systems. (Yeah, we discussed this at length before, and I'm sorry, but I just can't agree that corporate inertia is an excuse for failing to implement industry best practice for over a decade.) -- don
participants (7)
-
Don Stokes
-
Karl Hardisty
-
Mark Foster
-
Pete Mundy
-
Shane Langley
-
Simon Lyall
-
Tim Price