<div dir="ltr">Hi Thomas, obfuscating IP addresses doesn't help in the least. <a href="http://ns1.sleepyvalley.net">ns1.sleepyvalley.net</a> cannot be resolved, nor can we query it directly due to that.<div><br><div>Did you register the nameserver <a href="http://ns1.sleepyvalley.net">ns1.sleepyvalley.net</a> with your domain registrar?</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 26, 2018 at 12:44 PM, Thomas Strike <span dir="ltr"><<a href="mailto:thomas.strike@gmail.com" target="_blank">thomas.strike@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>I have been fighting a problem of setting up a new Bind9.9
primary authoritative server on the Internet for over 2 weeks now.
My hosted secondary server cannot be set up until my primary
server comes alive on the Internet. I have fought my domain name
provider for over 2 weeks trying to get my new server propagated
throwout the Internet and they say that the problem is with my
server. This is very perplexing because there are at least 4 DNS
servers out there that see my server and respond to all queries
successfully that land on my server but no other server can see
mine. It's hard to believe that the problem is on my end.</p>
<p>I am here asking for fresh sets of eyes to look at my setup file
and the domain zone record that is at issue. My domain is
<a href="http://sleepyvalley.net" target="_blank">sleepyvalley.net</a> and my primary dns server is
<a href="http://ns1.sleepyvalley.net" target="_blank">ns1.sleepyvalley.net</a>. Standard A records that should resolve are
www., ftp., and <a href="http://mail.sleepyvalley.net" target="_blank">mail.sleepyvalley.net</a>.</p>
<p>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------<br>
</p>
<p><u>named.conf:</u><br>
</p>
<p>acl trusted-servers {<br>
144.x.x.x.; // <a href="http://ns1.sleepyvalley.net" target="_blank">ns1.sleepyvalley.net</a><br>
8..x.x.x; // <a href="http://sdns1.ovh.ca" target="_blank">sdns1.ovh.ca</a><br>
};<br>
<br>
options {<br>
listen-on port 53 { any; };<br>
listen-on-v6 port 53 { any; };</p>
<p>// I have IPv6 implemented on my server but could it be an IPv6
issue?</p>
<p> allow-query { any; };<br>
<br>
recursion yes;<br>
allow-recursion {<br>
any;<br>
}; <br>
allow-transfer {<br>
trusted-servers;<br>
};<br>
</p>
<p> directory "/var/named";<br>
dump-file "/var/log/named/data/cache_<wbr>dump.db";<br>
statistics-file "/var/log/named/data/named_<wbr>stats.txt";<br>
memstatistics-file "/var/log/named/data/named_<wbr>mem_stats.txt";<br>
<br>
notify yes; <br>
<br>
</p>
<p>// I am not familiar with what dnssec does. Is it necessary for a
primary DNS server to run properly?</p>
<p> dnssec-enable yes;<br>
dnssec-validation yes;<br>
dnssec-lookaside auto;<br>
</p>
<p>// Could this be a security key management issue?</p>
<p> bindkeys-file "/etc/named.iscdlv.key";<br>
managed-keys-directory "/var/named/dynamic";<br>
<br>
pid-file "/run/named/named.pid";<br>
session-keyfile "/run/named/session.key";<br>
};include "/etc/named.logging";<br>
<br>
zone "." IN {<br>
type hint;<br>
file "<a href="http://named.ca" target="_blank">named.ca</a>";<br>
};<br>
<br>
include "/etc/named.rfc1912.zones";<br>
include "/etc/named.root.key";<br>
<br>
zone "<a href="http://sleepyvalley.net" target="_blank">sleepyvalley.net</a>" {<br>
type master;<br>
file "/var/named/<a href="http://sleepyvalley.net">sleepyvalley.net</a>.<wbr>hosts";<br>
allow-transfer { trusted-servers; };<br>
};<br>
key rndc-key {<br>
algorithm hmac-md5;<br>
secret "xxxxxxxxxxxxxxxxxxxxxxxx";<br>
};<br>
controls {<br>
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { rndc-key;
};<br>
};<br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>--------------</p>
<p><u><span>sleepyvalley.net.hosts:</span></u></p>
<p><u><span>/</span></u><u><span>/
I am a little confused about the Time-To-Live in this record.
<br>
</span></u></p>
<p><u><span>// Which of these 2 ttls do resolvers
use to cache their answers for?</span></u></p>
<p>$ttl 38400<br>
<a href="http://sleepyvalley.net" target="_blank">sleepyvalley.net</a>. IN SOA <a href="http://ns1.sleepyvalley.net" target="_blank">ns1.sleepyvalley.net</a>.
<a href="http://administrator.sleepyvalley.net" target="_blank">administrator.sleepyvalley.net</a><wbr>. (<br>
1526060969<br>
1H<br>
3600<br>
5M<br>
300 ) // short 5 min. ttl for testing.<br>
<a href="http://sleepyvalley.net" target="_blank">sleepyvalley.net</a>. IN A 144.x.x.x.x<br>
<a href="http://mail.sleepyvalley.net" target="_blank">mail.sleepyvalley.net</a>. IN MX 10 <a href="http://mail.sleepyvalley.net" target="_blank">mail.sleepyvalley.net</a>.<br>
<a href="http://mail.sleepyvalley.net" target="_blank">mail.sleepyvalley.net</a>. IN A 144.x.x.x.x<br>
<a class="m_4644449055346307236moz-txt-link-abbreviated" href="http://www.sleepyvalley.net" target="_blank">www.sleepyvalley.net</a>.
IN A 144.x.x.x.x<br>
<a class="m_4644449055346307236moz-txt-link-abbreviated" href="ftp://ftp.sleepyvalley.net" target="_blank">ftp.sleepyvalley.net</a>.
IN A 144.x.x.x.x<br>
<a href="http://ns1.sleepyvalley.net" target="_blank">ns1.sleepyvalley.net</a>. IN A 144.x.x.x.x<br>
<a href="http://sleepyvalley.net" target="_blank">sleepyvalley.net</a>. IN NS <a href="http://ns1.sleepyvalley.net" target="_blank">ns1.sleepyvalley.net</a>. //
Primary DNS service<br>
<a href="http://sleepyvalley.net" target="_blank">sleepyvalley.net</a>. IN NS <a href="http://sdns1.ovh.ca" target="_blank">sdns1.ovh.ca</a>. //
Secondary externally hosted DNS service.<br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>----------------</p>
<p>Any insights would be gratefully appreciated. Thanks in advance.<br>
</p>
</div>
<br>______________________________<wbr>_________________<br>
Please visit <a href="https://lists.isc.org/mailman/listinfo/bind-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/bind-users</a> to unsubscribe from this list<br>
<br>
bind-users mailing list<br>
<a href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/bind-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/bind-users</a><br>
<br></blockquote></div><br></div>