BIND 9.2.2 Resolution of hostnames in NOTIFY SET

Hi,

Does anyone know how BIND resolves the hostnames in the NOTIFY SET?
Does it refer to the zone file from which the NS records are pulled or
does it use the answer given by the NS servers in the OS resolv.conf?

I need NOTIFY to work between a MASTER and a SLAVE that run on
internal addresses but deal with zone files that contain public
addresses.

I can get NOTIFY to work when dealing with *only* internal addresses,
but not when I introduce external addresses ie where the address of a
host in the zone file is different to the one that would normally be
resolved using resolv.conf servers.

thx

Garreth

garreth.mcdaid@sabre-ots.com (Garreth McDaid) wrote in message news:<2e54aff8.0408030916.4bae05e5@posting.google. com>...
> Hi,
>
> Does anyone know how BIND resolves the hostnames in the NOTIFY SET?
> Does it refer to the zone file from which the NS records are pulled or
> does it use the answer given by the NS servers in the OS resolv.conf?
>
> I need NOTIFY to work between a MASTER and a SLAVE that run on
> internal addresses but deal with zone files that contain public
> addresses.
>
> I can get NOTIFY to work when dealing with *only* internal addresses,
> but not when I introduce external addresses ie where the address of a
> host in the zone file is different to the one that would normally be
> resolved using resolv.conf servers.
>
> thx
>
> Garreth


> Does anyone know how BIND resolves the hostnames in the NOTIFY SET?
> Does it refer to the zone file from which the NS records are pulled or
> does it use the answer given by the NS servers in the OS resolv.conf?

BIND resolves the names in the NOTIFY set using the named daemon of
which the zone file forms a part, therefore NOTIFY fails when the
SLAVE is on running on a NS Server that listens on a different (eg
internal/private) address. You can verify this by turning on debugging
iwth "rndc trace 1".

The "also-notify" facility doesn't resolve this problem either,
because also-notify only works *after* the initial NOTIFY takes place.
It the initial NOTIFY doesn't work, "also-notify" seems to be
cancelled.

You could put a third NS record in the zone file that resolves
directly to an internal address, but that's not something I'd
recommend.

Garreth