Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On my linux machine I have:
- one physical interface eth0 with the public ip x.x.x.x
- one logical interface eth0:0 with the public ip t.t.t.t
- BIND DNS listening to t.t.t.t

If I ping t.t.t.t from any other place, it responds back, so that's good.
What I'm trying to do is set up BIND to use the t.t.t.t ip for zone exchange, the only bad thing is that traffic returning from the master server is going back to x.x.x.x.
I have tried some SNAT but I didn't quite hit the spot, traffic did match my rule but the master BIND would still reply to x.x.x.x.

Any ideas?

share|improve this question
up vote 1 down vote accepted

BIND has a transfer-source option that controls which local address is used to fetch zones. Add it to the options section of named.conf:

options {

    // ...

    transfer-source t.t.t.t;

With this option set, BIND will send out transfer request messages from t.t.t.t. Responses from the master will then be sent back to t.t.t.t. You will also need to configure the master to accept zone transfers from t.t.t.t (if you've not done so already).

You might also like to set the query-source and notify-source options to control which local address is used for making queries and sending notify messages respectively:

query-source address t.t.t.t;
notify-source t.t.t.t;

Further documentation for these options can be found in the BIND Administrator Reference Manual, available from the BIND documentation page.

share|improve this answer
Thank you for the help! It worked. – w00t Jun 19 '10 at 12:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.