Help: DNS and Dynamic DNS

Scott Taylor staylor at coloradomusic.com
Tue Feb 27 22:50:59 UTC 2001


Something I ran across when having DDNS and DHCP on the same server is that DHCP
tries to contact DNS across the loopback address, so 127.0.0.1 needed to be in the
allow-updates list (though I have the machine's registered IP address in the
allow-updates list too for completeness)


Kevin Darcy wrote:

> What is it exactly that you are trying to update? If you're trying to add a
> "qwq.qdot.com" A record, then the status of the zone file for
> 10.168.192.in-addr.arpa is entirely irrelevant. Looks like server #1 is
> authoritative for "qdot.com", but the zone is not enabled for Dynamic Update.
> And it looks like server #2 is a lame delegation, i.e. it's not authoritative
> for "qdot.com" at all.
>
> - Kevin
>
> Thomas B wrote:
>
> > Anyone know how to get Dynamic DNS (nsupdate) to work? I probably have a
> > config problem, but I can't find it.
> >
> > I have our subnet configured with the "allow-update" option set in the
> > named.conf. The log file shows "Dynamic zone file db.192.168.10 is
> > writable", so it appears writable.
> >
> > The allow-update option is set to the ip address of the dns server (which is
> > the same server the nsupdate program is run from)
> >
> > But when I send the update, I get the following message: (the domains and IP
> > addresses have been changed to protect the guilty).
> >
> > res_mkupdate: packet size = 49;; res_send()
> > ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 4462
> > ;; flags:; ZONE: 1, PREREQUISITE: 0, UPDATE: 1, ADDITIONAL: 0
> > ;;      qdot.com, type = SOA, class = IN
> > qwq.qdot.com.        3w6d19h46m40s IN A  192.168.10.5
> > ;; Querying server (# 1) address = 192.168.10.20server rejected query:
> > ;; ->>HEADER<<- opcode: UPDATE, status: REFUSED, id: 4462
> > ;; flags: qr ra; ZONE: 1, PREREQUISITE: 0, UPDATE: 1, ADDITIONAL: 0
> > ;;      qdot.com, type = SOA, class = IN
> > qwq.qdot.com.        3w6d19h46m40s IN A  10.1.6.5
> > ;; Querying server (# 2) address = 138.58.53.22;; got answer:
> > ;; ->>HEADER<<- opcode: UPDATE, status: NOTAUTH, id: 4462
> > ;; flags: qr ra; ZONE: 0, PREREQUISITE: 0, UPDATE: 0, ADDITIONAL: 0
> >
> > This message shows the update was refused, but the log clearly shows that
> > the zone is writable (log not listed).



More information about the bind-users mailing list