alternate port / alternate way for master DNS zone xfers ?

[Jim Reid]

>>>>> "Gary" == Gary Stainburn <gary.stainburn at ringways.co.uk> writes:

    Gary> I know I'm jumping into this a bit late on, but I have a similar problem.
    Gary> I have my own network with it's own DNS and it all works fine. 
    Gary> My problem is that I have a link to someone else's network
    Gary> using a CISCO ISDN router that i have no control over.  My
    Gary> problem is that I cannot get my DNS to forward requests for
    Gary> their DNS through the router.  If I nslookup using their
    Gary> server it works fine, but if I use my server it fails.  I
    Gary> need my named to talk to their named as though it was a
    Gary> client and not a named itself.  Is this possible?

There are two ways to do this. One is to configure your name server as
a slave (secondary) for the other party's zones. The second option is
to configure your name server as a forwarding server for the other
party's zones.

The first option is probably better. You'll get the occasional zone
transfer and your name server will make SOA queries to the other name
server. If you go for the second option, you need an up to date
release of BIND8.2. It could also mean that most lookups of the other
party's name space brings up the ISDN line as your server forwards the
query to their name server. With the first approach, this would only
happen when your server checks the other party's SOA records. It will
depend on how they set up their zone files - and how often they change
them! - and how often you lookup their names which of these approaches
costs the most in ISDN charges.