Thanks Mike. I'm looking at the Secondary DNS service from dyndns now as they seem to provide what you're describing. This may be a silly question but looking at dyndns setup instructions they say as part of the setup I need to "...enter the IP address of your primary DNS server in the Master Server IP field". I understand why they need this but is the "Master Server IP" the same IP I get if I ping NS1.SCALR.NET or is it something else? If it's something else how do I find it?
Thanks again Mike, very useful info there. On Apr 16, 9:47 pm, mikeytag <[email protected]> wrote: > DNS zone transfer, also sometimes known by its (most common) opcode > mnemonic AXFR, is a type of DNS transaction. It is one of the many > mechanisms available for administrators to employ for replicating the > databases containing the DNS data across a set of DNS servers. (http:// > en.wikipedia.org/wiki/DNS_zone_transfer) > > Let me start by saying I have not done zone transfers with Scalr yet > as I am inside the US and don't have the latency issue. However, I > have done zone transfers before when I had servers in a colocation > facility. It allows you to have slave dns servers that get replicated > with whatever changes you do on the master servers. So here is how it > would work for Scalr. > > 1. You setup your own server somewhere, hosted on Amazon or something > else, that is your own DNS server. > 2. You configure bind on that server to accept zone transfers from the > Scalr DNS server ips. > 3. You point your domains to your own DNS servers. That means changing > them from ns1.scalr.net, ns2.scalr.net, etc. to ns1.myowndomain.com, > ns2.myowndomain.com > 4. Whenever you make changes to your Scalr farm that would affect a > DNS change, Scalr's DNS servers would then replicate the changes to > your own DNS servers. Since all your visitors would hit your DNS > servers, you would no longer have the latency involved with visitor's > hopping to the US and hitting Scalr's DNS. > > Here is a tutorial on setting up zone transfers for bind if you are > interested:http://www.zytrax.com/books/dns/ch7/xfer.html > > Hope that helps somewhat. > Mike > > On Feb 17, 8:58 am, "[email protected]" > > <[email protected]> wrote: > > Sorry to bang on about this. Can someone expand on what zone transfer > > actually does and whether it allows me to manage DNS from withinEurope? I > > really want to remove cross Atlantic hops. > > > TIA. > > > On Feb 6, 4:20 pm, "[email protected]" > > > <[email protected]> wrote: > > > Thanks, when I looked at the "zone transfers" link I wasn't entirely > > > sure if that was what I wanted. Very simply does that let me manage > > > all DNS via GoDaddy (for example)? If so is there any help on doing > > > this? > > > > TIA. > > > > On Feb 6, 4:13 pm, Nickolas Toursky <[email protected]> wrote: > > > > > For now, Scalr supports zone transfers to your nameservers. > > > > European DNS management is on our to-do. > > > > > On Feb 2, 5:25 pm, "[email protected]" > > > > > <[email protected]> wrote: > > > > > Hi, > > > > > > Now it's possible to setup EC2 inEuropeis there any chance of either > > > > > (a) scalr introducing european dns management, (b) being able to use > > > > > our own DNS? > > > > > > The obvious reason is that we incur more hops and higher latency > > > > > between hops when using US based DNS. > > > > > > Thanks, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
