check-integrity complains while deleting MX record with no A record, but not while deleting.
Mark Andrews
Mark_Andrews at isc.org
Mon Oct 29 11:29:59 UTC 2007
> I am using bind9.4.1-P1
>
> I am using nsupdate to add MX records
>
> I added an MX record that does not refer to an A record.
> ie:
>
> update add test.net. 500 IN MX 1 ddd.test.net.
>
> There is no A record for "ddd.test.net."
>
> It allows me to do this with no complaints.
>
> However, when I try to delete this record with
> update delete test.net. 500 IN MX 1 ddd.test.net.
> I get
> update failed: REFUSED
>
>
> This behavior continues until I set check-integrity no;
> in the options clause.
>
> The following settings made no difference:
>
>
> check-names master ignore;
> check-mx ignore;
> check-mx-cname ignore;
>
>
> My question is:
>
> Shouldn't it also complain while ADDing the MX record
Yes. If you check the upcoming fixes on the web page
or 9.4.2rc1 you will see that this is fixed.
> Having it complain while trying to delete a bad record seems
> problematic. If I have a misconfigured record, I have to reset
> check-integrity to no,
> delete the bogus record, and the set check-integrity back to yes?
>
>
> --
> Jack Tavares
> Reminder: I am at GMT+2, 10 hours AHEAD of Seattle.
> My workweek is Sunday-Thursday.
> Email sent to me Thursday afternoon (PST) may not be viewed until Sunday
> morning (GMT+2).
>
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list