Thanks Kevin, I had overlooked the . at the end. That along with using of subdomain in the update policy did the trick. previously i was using the wildcard option compared to the the subdomain option. I have to say, this group is excellent, with people giving great suggestions asap. This is highly needed in such complicated matters as the nameserver management. Wonderful work by you people. Thanks again. On Friday 16 May 2008 3:23:21 pm Kevin Darcy wrote: > Raghavendra Guru wrote: > > Hello, > > I am having a problem with nsupdate , or rather dont know the exact > > symantics to use for doing the nsupdate. Can somebody point me in the > > correct direction please ? > > > > I have a zone like > > example.com within that further domains like > > www.example.com > > ftp.example.com > > sftp.example.com etc. > > > > > > So When i generate a hmac key and associate it with the "example.com" > > zone i can successfully do the updates for > > www.example.com > > ftp.example.com > > sftp.example.com etc. > > > > > > But i'm unable to do the update for the root record, in this case > > example.ccom > > > > that is denoted in the zone file like > > > > @ IN A 201.201.202.222 > > > > > > If i try to do an nsupdate on for just "example.com" I get the message > > NOT AUTH from the server. > > > > Can anyone please help on whats the syntax to use when doing nsupdate > > to the root domain of a zone. > > "Root domain" is confusing; I usually use the term "apex". > > I've never had a problem nsupdate'ing the apex of the zone. Just spell > the zone name out and make sure to terminate it with a dot: > > "update add example.com. 86400 a 1.2.3.4" > > or > > "update add example.com. 86400 mx 10 smtp.example.com." > > > - Kevin This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. -- Attached file included as plaintext by Ecartis -- This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.