Hot answers tagged

3

While this ventures very close to being an opinion based question, I'm going to go ahead and say that this is objectively a bad idea. You're falling into the classic trap of over-engineering something that doesn't need to be over-engineered. Most reputable DNS administrators (i.e. known names) would criticize this as a bad practice. I don't have to ask ...


3

There is no query based way to get server state. Glue, negative cache timers, etc. must be dumped from memory using the rndc dumpdb command. Record types beginning with \- are negatively cached. \-A, \-AAAA, etc. \-ANY indicates a true NXDOMAIN. No records live alongside or beneath this entity. The above might be confusing if you have not been exposed to ...


2

The original behavior is that slaves periodically perform a check that their zone data is current, based on comparing the SOA SERIAL field, with an interval specified in the SOA REFRESH field. If the slave's local data is old it will trigger a zone transfer (IXFR/AXFR). In addition to this, if the master sends a notify message that will trigger this same ...


1

It can't be done the way you want to achieve it. View matching stops at the first match, and outside views, only one default set of entries can exist. A client can match only one set of zones. You could have all your views contain all of the zone definitions you want to serve to clients (in your example, 192.168.1.200 should be in "teens" acl only, and the "...


1

I checked port 53 using telnet 138.201.14.109 53 and found out that is was blocked. I had forgotten to reload firewall after adding port 53 to listen to both TCP and UDP protocols. Just shared my mistake for someone else who maybe do the same.



Only top voted, non community-wiki answers of a minimum length are eligible