Will adding the following to the zone record allow AXFR? or can I
replace allow-transfer with allow-axfr and leave off the provide-ixfr line?
allow-transfer {
127.0.0.1;
212.13.194.70;
209.237.247.198;
209.20.91.73;
};
provide-ixfr no ;
I noticed that some of the nameservers have the same IPs as the old
ones; would a request for
during the interim until my registrar updates the
nameservers for ilovephilosophy.com?
and will the following input and output rules in iptables suffice to
allow zone transfers:
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
Thanks,
Mike
Andy Smith wrote:
When changing nameservers on a live domain I would
generally do the
following:
1. Make sure the zone is loaded on the primary name server and it
serves up the correct info when queried.
2. Make sure it's loaded on the other nameservers in the set, and
that they all serve up the correct info.
3. Change the nameservers at the registrar by whatever means they
provide for that.
I don't think you have done step 2 yet, which you will need to do
whether you're going to put your nameserver plus the bitfolk ones or
just the bitfolk ones into your registrar's NS list.
You will need to add the IPs in allow-axfr, make sure tcp/53 is open
from them, contact support and wait for confirmation that it's set
up.
Cheers,
Andy
On Wed, Oct 13, 2010 at 02:57:12PM -0400, Michael Corliss wrote:
That did it, thanks!
2 follow-up questions:
-My registrar still has the old Bitfolk nameservers listed, how can I
have them change to the new ones seamlessly? Does it make sense to do it
stepwise, i.e. add the correct nameservers, have my host switch to them,
and them move the old ones?
-If I want to use my DNS as a hidden DNS, so that all requests still come
through the Bitfolk secondaries, is it sufficient to add an
allow-transfer section of named.conf.local with their IPs in it?
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users