This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Previous message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Next message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Fri Dec 2 13:13:16 CET 2005
Hi,
On Thu, Dec 01, 2005 at 07:28:41PM +0300, Max Tulyev wrote:
> Stop. You have 10000 domains. You have IP address(es) from ISP A . You are
> moving to ISP B with OTHER address(es). And you don't need to send 10000
> modify requests for these 10000 domains to change A (NS, MX) records. Where
> is the magic? ;-)
Be primary DNS for those 10000 domains, run a perl/sed/... script on the DNS
zones to replace all the IPs from ISP A with IPs from ISP B.
Send out two e-mails to update the IP of your primary nameserver:
- to your secondary name server operators (DNS slaves)
- to the TLD that contains your nameserver, to get the glue record updated
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 81421
SpaceNet AG Mail: netmaster at Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234
- Previous message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Next message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]