Re: How to request ixfr updates against public ip directly instead of unicast ip in bind
In article , Matus UHLAR - fantomas wrote: > On 12.10.16 20:57, rams wrote: > >I have master and slave servers. When we have updates in master, slave is > >getting updating after 20 or 30 minutes. > >When I look into tcpdump pcakets, Slave is trying with master unicast ip to > >get updates. We don't have port opened slave to master with unicast ip and > >we have port opened slave to master with public ip. > > > >Do we have any option checking for SOA value directly with public ip of > >master instead of unicast ip. > > I don't get it. What do you mean by "unicast" and "public" IP? My guess was that he's doing Anycast DNS for his public IP, and the unicast address is the real address that the router forwards to. Or he's just confused about terminology, and used "unicast IP" to mean "private IP" -- Barry Margolin Arlington, MA ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
update failed: not authoritative for update zone (NOTAUTH)
Hi, Greetings !!! I am getting the following error when we do updates to bind even we have configured allow-update ANY, named folder is having all permissions and also owner ship. updating zone 'xtldprimary.com/IN': update failed: not authoritative for update zone (NOTAUTH) Kindly some one help me to resolve this issue. Thanks & Regards, Ramesh ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: update failed: not authoritative for update zone (NOTAUTH)
In message , rams writes: > Hi, > Greetings !!! > I am getting the following error when we do updates to bind even we have > configured allow-update ANY, named folder is having all permissions and > also owner ship. > > updating zone 'xtldprimary.com/IN': update failed: not authoritative for > update zone (NOTAUTH) > > > Kindly some one help me to resolve this issue. Read the error message. Named is not authorative (configured) for the the zone to be updated. > Thanks & Regards, > > Ramesh -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: update failed: not authoritative for update zone (NOTAUTH)
To be clear, the zone is defined in named.conf -- otherwise the original poster would have never said that "allow-update" was configured for the zone -- but there is something wrong with the configuration, or in the zone file itself, that is preventing it from being properly loaded and served. You (original poster) should probably look at the logs from the last named startup to see if there were any problems parsing the config, or loading the zone file. Another possibility, if you're running views, is that your dynamic update is matching the wrong view, in which the zone is defined differently, or possibly not at all. - Kevin -Original Message- From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Mark Andrews Sent: Thursday, October 13, 2016 4:00 PM To: rams Cc: bind-users Subject: Re: update failed: not authoritative for update zone (NOTAUTH) In message , rams writes: > Hi, > Greetings !!! > I am getting the following error when we do updates to bind even we > have configured allow-update ANY, named folder is having all > permissions and also owner ship. > > updating zone 'xtldprimary.com/IN': update failed: not authoritative > for update zone (NOTAUTH) > > > Kindly some one help me to resolve this issue. Read the error message. Named is not authorative (configured) for the the zone to be updated. > Thanks & Regards, > > Ramesh -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Auto zone signing
I recently set up DNSSEC using some older tutorials and today found one for auto zone signing. My question, are there any gottchas in converting over from manual to auto? Larry Stewart, CISSP Contractor - ManTech Network Engineer Office: 520-538-4227 DSN: 879-4227 Cell phone: 520-227-8251 larry.c.stewart@mail.mil smime.p7s Description: S/MIME cryptographic signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Master/Slave communication not working if I use HMAC-SHA* algorithms when views are implemented
Hi, Can anybody implemented master/slave communication with views and algorithm HMAC-SHA* algorithms. I tried with all the HMAC-SHA* algorithms it didn't work for me, only HMAC-MD5 algorithm worked for communication. If anybody has any idea please help me. Thanks. -- Thanks, Nagesh Thati ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
