nsupdate not working /rndc freeze-unfreeze not working

techmom50 · 09-17-2013, 01:06 PM

All,
I have followed the man page for nsupdate and the Bind 9 admin guide and i still cannot get these two to work properly
nsudate returns "Couldn't get address for 'ns.mydomain.com': not found

and rndc freeze mydomain.zone returns rndc: 'freeze' failed: not found
I have bind-tools 9.9.2.2 on Gentoo 12.1 with Bind 9.9.2
any assistance for troubleshooting would be appreciated.

smallpond · 09-17-2013, 03:37 PM

Does this work?

Code:

dig NS mydomain.com @m.gtld-servers.net

The freeze failure will occur if the server is not master for the zone.

techmom50 · 09-17-2013, 04:37 PM

Quote:

This zone is my master Funny when i look back in the named.log this is what it showed:
16-Sep-2013 09:05:36.405 general: info: received control channel command 'freeze'
16-Sep-2013 09:05:36.405 general: info: freezing all zones: success
16-Sep-2013 09:05:49.778 general: info: received control channel command 'freeze pacificcabinets.zone'

and this is the result of the above dig for our domain:

Code:

dig NS mydomain.com @m.gtld-servers.net

Quote:

; <<>> DiG 9.9.2-P2 <<>> ns.tux.pacificcabinets.com @m.gtld-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11599
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ns.tux.pacificcabinets.com. IN A

;; AUTHORITY SECTION:
pacificcabinets.com. 172800 IN NS ns1.bluehost.com.
pacificcabinets.com. 172800 IN NS ns2.bluehost.com.

;; ADDITIONAL SECTION:
ns1.bluehost.com. 172800 IN A 74.220.195.31
ns2.bluehost.com. 172800 IN A 69.89.16.4

;; Query time: 269 msec
;; SERVER: 192.55.83.30#53(192.55.83.30)
;; WHEN: Tue Sep 17 14:34:53 2013
;; MSG SIZE rcvd: 132

smallpond · 09-17-2013, 06:30 PM

Looks like bluehost believes that they are the authoritative name server for the domain, and they are higher up the chain so they win. Unless ns1.bluehost.com is under your control, you can't make changes to the domain with nsupdate.

dig NS pacificcabinets.com @ns1.bluehost.com

; <<>> DiG 9.8.3-P1-RedHat-9.8.3-2.P1.fc15 <<>> NS pacificcabinets.com @ns1.bluehost.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61631
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;pacificcabinets.com. IN NS

;; ANSWER SECTION:
pacificcabinets.com. 86400 IN NS ns1.bluehost.com.
pacificcabinets.com. 86400 IN NS ns2.bluehost.com.

;; ADDITIONAL SECTION:
ns2.bluehost.com. 14400 IN A 69.89.16.4
ns1.bluehost.com. 14400 IN A 74.220.195.31

;; Query time: 95 msec
;; SERVER: 74.220.195.31#53(74.220.195.31)
;; WHEN: Tue Sep 17 19:22:53 2013
;; MSG SIZE rcvd: 114

techmom50 · 09-17-2013, 06:42 PM

So if I have to make any changes to my caching DNS server I have to:
1. stop named
2. delete the *.jnl files
3. re create the zones with additions or deletes
4. restart named
That seems ridiculous