Category: How to sync iworx DNS to a non-iworx DNS server

Share this post...Tweet about this on TwitterShare on Google+0Share on Facebook0
  • Step 1: Identify the IP address of your interworx primary nameserver (a.b.c.d)
  • Step 2: Identify the IP address of your bind secondary nameserver (e.f.g.h)
  • Step 3a: If you want to allow transfer of only a subset of the domains on the interworx server, on the interworx server run the following:
    echo 'e.f.g.h:allow,AXFR="site1.com/site2.com/site3.com"' >> /service/axfrdns-a.b.c.d/tcp
  • Step 3b: If you want to allow transfer of all the domains on the interworx server, on the interworx server run the following:
    echo 'e.f.g.h:allow' >> /service/axfrdns-a.b.c.d/tcp
  • Step 4: Recompile the TCP file so that it’s valid.
    cd /service/axfrdns-a.b.c.d/
    make
  • Step 5: Restart the AXFRDNS service.
    svc -t /service/axfrdns-*
  • Step 6: Test from the bind server, like this:
    dig @a.b.c.d site1.com axfr
Citation Source: DNS
Nov 14, 2012, 3:15 pmBy: InterWorx
How to sync iworx DNS to a non-iworx DNS server
4 votes, 3.75 avg. rating (72% score)
(4) Comments
  1. Roman: Something like this for djbdns-1.05?
    November 4, 2014 at 4:55 pm
    Reply
  2. MDeinhardt: Don't forget to enable the axfrdns shell user, otherwise it won't work. It's disabled by default...
    June 26, 2014 at 4:13 pm
    Reply
  3. InterWorx: This error could be the result of something blocking access to that IP -- definitely open up a ticket with your reseller's support team (or our help desk if you're a direct customer).
    May 12, 2014 at 5:05 pm
    Reply
  4. Jake: This does not work. dig @10.1.95.2 example.com axfr ;; communications error to 10.1.95.2#53: end of file
    April 24, 2014 at 9:22 am
    Reply

Leave a Reply
Surround code blocks with <pre>code</pre>

Your email address will not be published.

Comments

Broken Link