DNS transfer from one isp to another, secondary and ips

Search Again:

DNS transfer from one isp to another, secondary and ips
From: Caballero, Victor (Burbank)
Date: Sunday, May 26, 2002
Time: 2:34:50 pm
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C204FB.E377B210
Content-Type: text/plain

Hi,

Is there a reference for directing on how to change Quick DNS 3.5 when
changing isp new ip class and secondary dns setup.
Our dns is at ns.networkmags.com

1. we have a new ip class so all servers are changing ips. I need to
replace all ips from 209.85.25.x to 209.183.223.x.

2. we also have to change settings for secondary dns. Our server is a
primary dns.

Any help would be greatly appreciated.

This is what our new ISP Savvis is requesting.

> This is what you need to do before Savvis can provide secondary dns
> for
any domain.
>
> 1. Go to networksolutions.com and make sure that the following
> nameservers
are listed for your domain.
>
> yournameserver
> yoursecondary (if any)
> ns1.savvis.net 209.16.211.42
> ns2.savvis.net 204.194.10.206
> ns3.savvis.net 209.83.162.35
>
> Now the root.servers will point incoming lookups all of the above
nameservers.
>
>
> 2. Include the following NS records in your zone file.
>
> @ IN NS yoursnameserver
> @ IN NS yoursecondary (if any)
> @ IN NS ns1.savvis.net.
> @ IN NS ns2.savvis.net.
> @ IN NS ns3.savvis.net.
>
> Now any time you make a change bind will send out a notification to
> the
above nameservers.
>
>
> 3. Make sure you are not blocking zone transfers from all 3 Savvis
nameservers.
>
> 4. Notify Savvis that you would like secondary dns for that domain.

------_=_NextPart_001_01C204FB.E377B210
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">

<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C204C1.D55FCDA0">

<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

Hi,<o:p></o:p>

<o:p> </o:p>

Is there a reference for directing on how to change =
Quick
DNS 3.5 when changing isp
new ip class and secondary dns
setup.<o:p></o:p>

Our dns is at =
ns.networkmags.com<o:p></o:p>

<o:p> </o:p>

<ol style=3D'mso-margin-top-alt:0in' start=3D1 type=3D1>
<li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1;tab-stops:list =
.5in'>we have a new ip
class so all servers are changing ips. =
I need to
replace all ips from 209.85.25.x to
209.183.223.x. <o:p></o:p></=
li>
</ol>

<o:p> </o:p>

<ol style=3D'mso-margin-top-alt:0in' start=3D2 type=3D1>
<li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1;tab-stops:list =
.5in'>we also have to change =
settings
for secondary dns. Our server is a =
primary dns. <o:p></o:p></li>
</ol>

<o:p> </o:p>

Any help would be greatly
appreciated.<o:p></o:p>

<o:p> </o:p></f=
ont>

This is what our new ISP =
Savvis is =
requesting.<o:p></o:p>

<o:p> </o:p></f=
ont>

>
This is what you need to do before Savvis =
can provide
secondary dns <o:p></o:p>

>
for<o:p></o:p>

any
domain.<o:p></o:p>

>
<o:p></o:p>

>
1. Go to networksolutions.com and make sure that the following =
<o:p></o:p>

>
nameservers<o:p></o:p>

are
listed for your domain.<o:p></o:p>

>
<o:p></o:p>

>
yournameserver<o:p></o:p>

>
yoursecondary =
(if any)<o:p></o:p>

>
ns1.savvis.net  =
209.16.211.42<o:p></o:p>

>
ns2.savvis.net  =
204.194.10.206<o:p></o:p>

>
ns3.savvis.net  =
209.83.162.35<o:p></o:p>

>
<o:p></o:p>

>
Now the root.servers will point incoming =
lookups all
of the above<o:p></o:p>

nameservers.<o:p></o:p>

>
<o:p></o:p>

>
<o:p></o:p>

>
2. Include the following NS records in your zone =
file.<o:p></o:p>

>
<o:p></o:p>

>
@   IN    NS    yoursnameserver<o:p></o:p>

>
@   IN    NS    yoursecondary (if
any)<o:p></o:p>

>
@   IN    NS    =
ns1.savvis.net.<o:p></o:p>

>
@   IN    NS    =
ns2.savvis.net.<o:p></o:p>

>
@   IN    NS    =
ns3.savvis.net.<o:p></o:p>

>
<o:p></o:p>

>
Now any time you make a change bind will send out a notification to =
<o:p></o:p>

>
the<o:p></o:p>

above
nameservers.<o:p></o:p>

>
<o:p></o:p>

>
<o:p></o:p>

>
3. Make sure you are not blocking zone transfers from all 3 Savvis<o:p></o:p>

nameservers.<o:p></o:p>

>
<o:p></o:p>

>
4. Notify Savvis that you would like =
secondary dns for that domain.<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p></f=
ont>

<o:p> </o:p>

</div>

</body>

</html>

------_=_NextPart_001_01C204FB.E377B210--

Messages In This Thread:

DNS transfer from one isp to another, secondary and ips by Caballero, Victor (Burbank) on May 26, 2002 at 2:34:50 pm
- Re: DNS transfer from one isp to another, secondary and ips by Len Conrad on May 26, 2002 at 4:05:46 pm

Return to Digital Point Solutions' Home Page