dyn. dns-update

Tom Horstmann webmaster at 7thweb.de
Fri Nov 16 13:51:45 UTC 2001




Cricket Liu schrieb:
> 
> > Debug gives some information, but i don't see any hints in there.
> > Do you??
> >
> > ;; Querying server (# 1) address = 217.172.161.46
> > server rejected query:
> > ;; ->>HEADER<<- opcode: UPDATE, status: REFUSED, id: 3190
> > ;; flags: qr ra; ZONE: 1, PREREQUISITE: 0, UPDATE: 1, ADDITIONAL: 0
> > ;;      7thweb.de, type = SOA, class = IN
> > test4.7thweb.de.        30S IN A        62.96.171.143
> > ;; Querying server (# 2) address = 195.94.83.15
> > server rejected query:
> > ;; ->>HEADER<<- opcode: UPDATE, status: REFUSED, id: 3190
> > ;; flags: qr ra; ZONE: 1, PREREQUISITE: 0, UPDATE: 1, ADDITIONAL: 0
> > ;;      7thweb.de, type = SOA, class = IN
> > test4.7thweb.de.        30S IN A        62.96.171.143
> > ;; res_nupdate: res_nsend: send error, n=-1 (Connection timed out)
> 
> Yeah.  The debug output says your update was refused by both of
> the 7thweb.de name servers.  Have you checked to make sure that
> the name servers allow updates from the address of the host on
> which you're running nsupdate?


That's been the problem. There had been no entries about updates.
Till now those entries weren't needed because updates were only
been made by changing the conf-files and restarting named. Don't
know why i could not read that out of the debug:))

Thank you so much.


Regards,

TomH
restarting named.


More information about the bind-users mailing list