Re: Best Practices: Slaves And Split Horizon Masters

2015-08-21 Thread Tim Daneliuk
On 08/21/2015 11:57 AM, Bob Harold wrote: > https://kb.isc.org/article/AA-00296/0/My-slave-server-for-both-an-internal-and-an-external-view-has-both-views-transferred-from-the-same-master-view-how-to-resolve-.html > > > > -- > Bob Harold > hostmaster, UMnet, ITcom > Information and Technology S

Re: Best Practices: Slaves And Split Horizon Masters

2015-08-21 Thread Bob Harold
https://kb.isc.org/article/AA-00296/0/My-slave-server-for-both-an-internal-and-an-external-view-has-both-views-transferred-from-the-same-master-view-how-to-resolve-.html -- Bob Harold hostmaster, UMnet, ITcom Information and Technology Services (ITS) rharo...@umich.edu 734-647-6524 desk On Fri

Best Practices: Slaves And Split Horizon Masters

2015-08-21 Thread Tim Daneliuk
I have a bind9 split horizon master with two views: internal and external. However, if attempt to populate a slave from it, the internal view leaks out and is visible to the world. Is there some best practice for running slaves from split horizon masters that I should be studying? Thanks, -- --

Re: DNSSEC secondary (free)

2015-08-21 Thread Mathew Ian Eis
I gathered what little I know from here: https://forums.he.net/index.php?topic=1006.0 where one of their admins says "DNSSEC records can be stored and served, but no additional processing is performed.” If you’re loading through zone transfers, this should be enough for secondary service - a

RE: Help DNS

2015-08-21 Thread Darcy Kevin (FCA)
nslookup is horrible. I'm assuming that the base query (ctc.cu) is getting REFUSED (probably due to lack of loopback in the allow-query-cache clause), then nslookup is stepping through the searchlist, getting one or more NXDOMAINs, and misreporting the overall failure as NXDOMAIN. If nslookup *

Re: Help DNS

2015-08-21 Thread Abdul Khader
Is 127.0.0.1 allowed to query in your named.conf ? On 8/21/2015 8:22 PM, Int wrote: Giving problem the DNS's resolution of names When I sell off a nslookup from localhost:127.0.0.1 in the servers DNS Bind9 Here what the DNS's log generates goes: For the following consultation to the DNS

Help DNS

2015-08-21 Thread Int
Giving problem the DNS's resolution of names When I sell off a nslookup from localhost:127.0.0.1 in the servers DNS Bind9 Here what the DNS's log generates goes: For the following consultation to the DNS # nslookup ctc.cu Server: 127.0.0.1 Address: 127.0.0.1 #53 ** server can't find ctc.cu: