check-integrity complains while deleting MX record with no A record, but not while deleting.
j.tavares at F5.com
Mon Oct 29 11:11:20 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.
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.
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;
My question is:
Shouldn't it also complain while ADDing the MX record
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?
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
More information about the bind-users