fac3less
01-12-2005, 01:27 AM
Hi all,
I have a few minor q's - its a whole lot easier starting from scratch than it is transferring over to another server..
Heres a few q's I have:
Mainly concerning DNS, rDNS:
The point being - say my dnservers are already pointed at a domain, i.e. ns1.mydomain.com and ns2.mydomain.com - would it be best to import (sync) the entire dns server with the previous server and then wait a bit, and then manually modify the IP's listed in the A entries for the names?
I'm attempting to transfer over with as 'little' downtime as possible, updated all the TTL's to 900, same with a few of the refreshes within the DNS system.
This is how I was thinking of doing it: importing the entire dns db, waiting a bit, dropkicking the old server and then manually changing the ip's to point to the new ones.
That said - I'm lacking the knowledge behind the dns system itself - are the root servers going to query my old DNS ip's and say 'oops no longer here' - and then hunt around for some new ones? or are the resolvers (assuming they are: 205.218.64.4 and 205.218.64.6) going to sort of give the root DNS a kickstart in saying 'we now have ns1.domain.com available here now')
And concerning rDNS - does it play any role other than for mail? just contact SFN and they'll update my boxes main IP with the rDNS but how does that work if theres a mimic existing - i.e. my old server with rev.domain.com and ns1.domain.com, ns2.domain.com existing. I'd rather not have to wipe the DNS on that side of things prior to having everything rolling over here.
I understand with the new DNS system in place (verizon's?) things are much faster, so I don't expect too much downtime to begin with but the less - the better.
Any ideas, hints, tips let me know!
Thanks!
//That said, great network - glad to be on it, didn't realize you guys were so young - companywise. Lets hope this goes well.
I have a few minor q's - its a whole lot easier starting from scratch than it is transferring over to another server..
Heres a few q's I have:
Mainly concerning DNS, rDNS:
The point being - say my dnservers are already pointed at a domain, i.e. ns1.mydomain.com and ns2.mydomain.com - would it be best to import (sync) the entire dns server with the previous server and then wait a bit, and then manually modify the IP's listed in the A entries for the names?
I'm attempting to transfer over with as 'little' downtime as possible, updated all the TTL's to 900, same with a few of the refreshes within the DNS system.
This is how I was thinking of doing it: importing the entire dns db, waiting a bit, dropkicking the old server and then manually changing the ip's to point to the new ones.
That said - I'm lacking the knowledge behind the dns system itself - are the root servers going to query my old DNS ip's and say 'oops no longer here' - and then hunt around for some new ones? or are the resolvers (assuming they are: 205.218.64.4 and 205.218.64.6) going to sort of give the root DNS a kickstart in saying 'we now have ns1.domain.com available here now')
And concerning rDNS - does it play any role other than for mail? just contact SFN and they'll update my boxes main IP with the rDNS but how does that work if theres a mimic existing - i.e. my old server with rev.domain.com and ns1.domain.com, ns2.domain.com existing. I'd rather not have to wipe the DNS on that side of things prior to having everything rolling over here.
I understand with the new DNS system in place (verizon's?) things are much faster, so I don't expect too much downtime to begin with but the less - the better.
Any ideas, hints, tips let me know!
Thanks!
//That said, great network - glad to be on it, didn't realize you guys were so young - companywise. Lets hope this goes well.