On Fri, 27 Oct 2006, Gerard Creamer wrote:
On 27/10/2006 12:39 p.m., Simon Lyall wrote:
How do people feel about a "best practice" document on this that we could encourage people to follow ( perhaps the DNC could publish) for people moving their domain between providers. Just the basics like, dropping the TTLs, getting all the servers data in the right order etc?
For what it's worth, I think it's a good idea. Wouldn't this be the sort of info InternetNZ or the DNC would publish on their site? Then everyone could link to it without having to worry about updates etc.
On a related matter - what is the course of action when an old domain provider continues to claim that they are primary for a domain, even when the name moved eons ago? The provider appears to be in denial over the issue, and it wouldn't be such a big deal if they weren't also a fairly large ISP (so are giving the wrong IP addresses to their own connectivity customers).
Ask them do a whois on the domain, and then point out that if they are carrying Authoritive NS records for a domain which the rootservers are pointing elsewhere - whois tells you this - they are breaking the DNS. If they won't address this, well, apart from encouraging all and sundry to boycott the organisation in question, it could questionably be considered a Denial of Service... In _most_ cases its usually a case of 'oh, by the way, spotted you're still hosting this zone, whois disagrees' and the typical response is 'oh, whoops, ok we'll fix that'. I havn't seen many providers refuse to purge legacy zones. Disclaimer: A backup of the zone files is a good idea, in case they need to be put back for whatever reason... Also notifying the client that its happened is smart.... DNS registries that automatically notify the SOA contact / Technical Contact / Domain Owner of changes to authoritive NS when actioned in the registry, are quite useful here... at least then the providers concerned all get a headsup that changes are afoot. IMHO. Mark.