one more nsupdate question..
j.tavares at F5.com
Mon Dec 10 08:18:21 UTC 2007
That is unfortunate.
I was pretty sure I was out of luck, but I wanted to ask to make sure I wasn't missing
some "trick" somewhere.
I know that if I use a
for the record that the MX references
prereq yxrrset madman.test.net. A
update add test.net.500 in MX 123 madman.test.net.
I at least get a NXRRSET error, which is a little better.
From: bind-users-bounce at isc.org on behalf of Barry Margolin
Sent: Mon 12/10/2007 1:09 AM
To: comp-protocols-dns-bind at isc.org
Subject: Re: one more nsupdate question..
In article <fjgo9h$j9b$1 at sf1.isc.org>,
"Jack Tavares" <j.tavares at F5.com> wrote:
> Using bind9.4.2, if I attempt to add a MX record using nsupdate
> and there is no A record that matches I get a operation refused message.
> [I understand why it fails]
> What I would like to be able to do is to give a better error message
> back to my user.
> Is there anyway to get a better error message out of nsupdate?
> for example:
> > update add test.net. 500 in MX 123 madman.test.net.
> update failed: REFUSED
Unfortunately, since nsupdate uses the DNS protocol, and the protocol
has very limited error-reporting details, there's nothing nsupdate can
do to improve on this. The DNS protocol has about a half dozen error
codes, and none of them are specific to this.
Barry Margolin, barmar at alum.mit.edu
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users