change the SOA

[Jeff Reasoner]

Your question isn't particularly clear, especially the part about the
temporary nameservers pointing to the new SOA. However, it sounds like
the general concern is that changing the authoritative server in the SOA
will break name resolution for you domain.
My experience is that it will not. Most applications - http, smtp and
the servers that run them don't care about SOAs.

My concern would be making sure your registrar gets your parent domain
to update the delegation for your domain in a timely fashion when you
switch IP addresses. Especially if the old addresses no longer route to
your servers. Also, don't forget to contact RIPENET (?) about delegating
your new net block (or your new ISP if your subnet can't be delegated to
you). That can take a while, and can have a greater impact in terms of
mail delivery.

Jeff

Based on my experience, the info in the 
On Wed, 2006-01-25 at 14:25, Aleksander wrote:
> Hi,
> 
> have some master dns records and their SOA is 
> "auto-generated-named.domain.com". The name is literally 
> "auto-generated-blahblah", this really sucks. We moved off that firewall 
> solution and now have the gateway running on a normal linux distro with 
> bind9. I'd like to clean up the records now. There's an IP change on the 
> way too, would be nice to clean up the records and lower TTL and the 
> same time.
> 
> Would it be fine, if I change the zones to have the SOA to be 
> domain.com. and add temporary nameservers 
> "auto-generated-name.domain.com" which point to the new SOA? Will this 
> break anything? And then notify the registrar etc.
> 
> In other words, if I change the SOA and let the old SOA name point to 
> the new one (NS record), will other hosts adapt the new SOA name? It's 
> important not to break the DNS for the hosts.
> 
> Put it more simply, what are the steps when changing the SOA?
> 
> Thanks,
> Alex
> 
>