You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device TP-LINK MR-3220 v2.1 and 2.3 and 2.4 tested, LEDE 17.01.1 version.
After installing bind-server, setting "option port '0'" for dnsmasq (to disable DNS configuration) and using provided named.conf file (below), resolution of domain names to IP addresses breaks down.
I was able to track down the problem. There is race condition in bringing interfaces up, starting nptd service and named service, resulting in:
named service beeing unable to open sockets and/or
ntpd service beeing unable to connect to ntp pool and set router time correctly and/or
incorrect time setting causes dnssec of named to reject proper answers for dns resolving.
With no named installed, the dnsmasq itself often starts too early, but this is masked by it beeing reinitialized on lan interface up event.
This is a known openwrt problem, the workaround is described here: https://dev.openwrt.org/ticket/19427
and involves creating a "netwait" service. I have tested this workaround and confirmed it works, however it is not nice.
Here my named.conf:
// This is the primary configuration file for the BIND DNS server named.
helgadeville:
Device TP-LINK MR-3220 v2.1 and 2.3 and 2.4 tested, LEDE 17.01.1 version.
After installing bind-server, setting "option port '0'" for dnsmasq (to disable DNS configuration) and using provided named.conf file (below), resolution of domain names to IP addresses breaks down.
I was able to track down the problem. There is race condition in bringing interfaces up, starting nptd service and named service, resulting in:
With no named installed, the dnsmasq itself often starts too early, but this is masked by it beeing reinitialized on lan interface up event.
This is a known openwrt problem, the workaround is described here: https://dev.openwrt.org/ticket/19427
and involves creating a "netwait" service. I have tested this workaround and confirmed it works, however it is not nice.
Here my named.conf:
// This is the primary configuration file for the BIND DNS server named.
acl locals {
localhost;
10.10.10/24;
};
options {
directory "/tmp";
};
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
The text was updated successfully, but these errors were encountered: