Re: Selective forwarding from an internal only name server

2016-08-19 Thread anup albal
Hi To clarify a bit. The server that runs ns1 has named listening on two addresses. One is an external facing address providing resolution to the queries coming from the internet. Lets call this ns.org.domain.name.au The other one internal facing and which is what ns1 is pointing to. There

Re: Selective forwarding from an internal only name server

2016-08-19 Thread S Carr
On 19 August 2016 at 07:25, anup albal wrote: > After that I cannot run a "dig sharepoint.com" or "dig microsoft.com" from > dns1. However it can resolve it if i run a "dig +trace sharepoint.com" or > "dig +trace microsoft.com" Can you post your full configs and the full dig outputs? Don't use +t

creating IPv6 interface eth0 failed; interface ignored

2016-08-19 Thread Wolfgang Riedel
Hi Folks, not sure if this is a bug or a feature but had been scratching my head for months now running BIND on Fedora22-24 and all the time I did a reboot BIND didn’t came up and I needed to restart the process to get it running. After some googling around I realized that I am not alone with t

Re: creating IPv6 interface eth0 failed; interface ignored

2016-08-19 Thread Mukund Sivaraman
On Fri, Aug 19, 2016 at 11:32:43AM +0200, Wolfgang Riedel wrote: > ### bootup with: empty-zones-enable no; > > [root@ns1 ~]# systemctl status named-chroot.service > ● named-chroot.service - Berkeley Internet Name Domain (DNS) >Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabl

Re: creating IPv6 interface eth0 failed; interface ignored

2016-08-19 Thread Wolfgang Riedel
Hi Mukund, yes this had been my fist assumption also but WHY should/would the statement "empty-zones-enable” within named.conf change the bring process of the network interface process? It’s courios, right? Wolfgang > On 19 Aug 2016, at 11:38AM, Mukund Sivaraman wrote: > > On Fri, Aug 19, 2

Re: creating IPv6 interface eth0 failed; interface ignored

2016-08-19 Thread Mukund Sivaraman
On Fri, Aug 19, 2016 at 11:46:36AM +0200, Wolfgang Riedel wrote: > Hi Mukund, > > yes this had been my fist assumption also but WHY should/would the > statement "empty-zones-enable” within named.conf change the bring > process of the network interface process? > > It’s courios, right? I suspect

Re: Selective forwarding from an internal only name server

2016-08-19 Thread anup albal
Hi Below are the options on the external name server. options { directory "/var/named"; pid-file "/var/named/tmp/named.pid"; forwarders { list.external.isp.forwarders; 127.0.0.1; }; query-sourceaddress externalLooking.ip.of.ns ; notify-source exter

Re: Selective forwarding from an internal only name server

2016-08-19 Thread S Carr
On 19 August 2016 at 09:02, anup albal wrote: > Below are the options on the external name server. That's not the full configs, and from both DNS servers. I get you don't want to expose some of the information but you're asking for help, we can't do that if you keep things back and obfuscate deta

Re: creating IPv6 interface eth0 failed; interface ignored

2016-08-19 Thread Sotiris Tsimbonis
On 19/8/16 12:38, Mukund Sivaraman wrote: > On Fri, Aug 19, 2016 at 11:32:43AM +0200, Wolfgang Riedel wrote: >> ### bootup with: empty-zones-enable no; >> >> [root@ns1 ~]# systemctl status named-chroot.service >> ● named-chroot.service - Berkeley Internet Name Domain (DNS) >>Loaded: loaded (/us

RE: bind used as resolver: matching the source ip

2016-08-19 Thread Darcy Kevin (FCA)
Or just check the RFCs. https://www.ietf.org/rfc/rfc5452.txt - Kevin -Original Message- From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Mukund Sivaraman Sent: Friday, August 19, 2016 2:27 AM To: pm8...@t-online.de Cc: bind

Re: DNS views setup help

2016-08-19 Thread Mathew Ian Eis
> where would I place it in the context of my views on the master? Inside of the view > Do I only need that one stanza on the master? I believe it is needed on the slave as well, to tell the slave to use the correct key when communicating with the master. That is how we are doing it… > Why in t