Hot answers tagged bind
At my request the poster came into our #powerdns IRC channel, where we quickly figured out that there was actually a typo between the domain names on master and slave - hidden by the obfuscation that was done to ask the question here.
The basic structure looks fine, but the NS records are bogus. The target must always point at a name, not an IP address. Assuming that you want the name of the target to exist in the newly created zone (based on your example), you will also need glue records. First zone: $ORIGIN example.com ; apex records omitted mysub IN NS ns1.mysub mysub IN NS ...
I'm guessing here, because you basically hid everything that was useful. Are you trying on purpose to make it hard to help you? It looks like you have an example.net entry in your domains table, but under that domain_id in the records table, you put example.org records. pdnsutil check-all-zones (or pdnssec if you're on 3.x) will probably notice this for ...
Yes, you can. RFC 1035 only specifies A domain-name which specifies the mailbox of the person responsible for this zone. It doesn't require the domain name to belong to the same zone. An example: dig soa serverfault.com ;; ANSWER SECTION: serverfault.com. 86400 IN SOA cf-dns01.serverfault.com. dns.cloudflare.com. ...
I don't think you can get BIND to do that. DNS isn't really designed with dynamic IP addresses in mind, so solving this entirely on the DNS level is likely to be quite tricky. I suspect your easiest option is to rsync the zone files over to the BIND host and then use ssh to do an rndc reload.
This is a common non-problem with BIND, though admittedly confusing. In recursive mode, BIND may return extra records that it is passively aware of, but will not actively attempt lookups for those records unless it is required to do so by the relevant standards. When this behavior is encountered with a single DNS server (i.e. the inconsistency is observed ...
Provided that you specified a file in the definition of the slave zone (it's common practice to do so), the zone data will be stored in that file and will be available across restarts. From the slave zone section of the manual: If a file is specified, then the replica will be written to this file whenever the zone is changed, and reloaded from this ...
This problem can be only reproduced with "vsftpd extended builds" taken from http://vsftpd.devnet.ru or from CentALT repository. I was not able to reproduce it any more with regular builds.
Only top voted, non community-wiki answers of a minimum length are eligible