Allowing zone xfer to slave server
Dawn Connelly
dawn.connelly at gmail.com
Thu Aug 30 21:40:56 UTC 2007
The command is actually:
dig @172.20.11.200 dss.la.gov axfr
You have to have the axfr for transfer. Otherwise it just queries for a
record rather than transfer.
I'm assuming that either dss-cs99la45-s1.dss.state.la.us or
dss-dr93la06-s1.dss.state.la.us resolves to 172.20.11.118?
The also-notify is only needed if there isn't an NS record.
Are there any messages in you log files that would provide a hint? Like does
your master server have any logs with your slaves IP address or does your
slave have any logs regarding this particular domain?
On 8/30/07, Ryan McCain <Ryan.McCain at dss.state.la.us> wrote:
>
> Here is the zone file from the primary DNS server if this helps..
>
> --
>
> $ORIGIN .
> $TTL 3600 ; 1 hour
> dss.la.gov IN SOA dssns.dss.la.gov. admin. (
> 53 ; serial
> 900 ; refresh (15 minutes)
> 600 ; retry (10 minutes)
> 86400 ; expire (1 day)
> 3600 ; minimum (1 hour)
> )
> NS dssns.dss.la.gov.
> NS dssns2.dss.la.gov.
> NS dss-cs99la45-s1.dss.state.la.us.
> NS dss-dr93la06-s1.dss.state.la.us.
> A 205.172.49.49
> MX 10 smtp-ext1.dss.la.gov.
> MX 20 smtp-ext2.dss.la.gov.
> $ORIGIN dss.la.gov.
> dss-cs99lv01-a A 205.172.49.5
> dssns A 199.248.209.34
> dssns2 A 199.248.209.35
> smtp-ext1 A 205.172.49.5
> smtp-ext2 A 205.172.49.7
> ryan A 205.172.49.100
> $ORIGIN .
>
>
>
More information about the bind-users
mailing list