0

I'm using my VPS provider's DNS servers as a slave, and to send them notifies, I use the also-notify function. They're making changes to the IP scheme of their DNS, which means I need to update my also-notify, which is fine, but I'm looking to future proof.

Today I have also-notify { 1.2.3.4; 4.5.6.7 }

Could I do this instead? also-notify { ns1.my-vps; ns2.my-vps }

Pat
  • 274
  • Look at the masters clause. – user Jun 16 '16 at 15:04
  • @MichaelKjörling I'm running a master DNS server, want to send notifies to slaves using hostname, not IP. This still looks like it's IP. From what I'm reading the IP is a requirement, so I don't think I'm able to do hostname – Pat Jun 16 '16 at 15:12
  • 1
    Is the slave named in the zone's NS RRs? If it is, then it should be receiving notifies already, and if it isn't, the whole exercise seems somewhat pointless. also-notify {} is for hosts which aren't named in zone NS RRs. – user Jun 16 '16 at 15:24
  • Michael is correct, you should be using NS records for this purpose. Refer to Why don't NS records contain IP addresses?. That said, it still doesn't get around the potential need to update glue records with your registrar. (i.e. if you had to provide these IPs to your registrar's web interface, they still need to be changed) – Andrew B Jun 16 '16 at 15:41

0 Answers0