Re: Selective forwarding from an internal only name server

orking. There is a firewall between the internal and external name servers. Other than ensuring that port53 is open between the two name servers for TCP and UDP traffic, is there anything else i need to check? Thanks Anup From: anup albal Sent: Friday, 19 August 2016

Re: Selective forwarding from an internal only name server

er it can resolve it if i run a "dig +trace sharepoint.com" or "dig +trace microsoft.com" On the internal clients talking to dns1, I get an NXDOMAIN response. --Anup ________ From: anup albal Sent: Thursday, 18 August 2016 10:04 AM To: BIND Users S

Re: Selective forwarding from an internal only name server

Hi Kevin Does that mean I setup another forwarding zone called microsoft.com or sharepoint.microsoft.com or both? And then do i need to add NS record entries similar to sharepoint.com in the fake root file? Regards Anup From: anup albal Sent: Thursday

Re: Selective forwarding from an internal only name server

org.domain.name.au ;; ADDITIONAL SECTION: ns1.org.domain.name.au. 86400 IN A ip.of.ns1 ;; Query time: 26 msec ;; SERVER: ip.of.dns1#53(ip.of.dns1) ;; WHEN: Thu Aug 18 09:38:09 2016 ;; MSG SIZE rcvd: 84 Regards Anup From: Chris Buxton Sent: Thursday, 18 Aug

Selective forwarding from an internal only name server

Hi First up apologies if this is not the right list to email and for a long email. I am hoping you can give me a clue as to what I am doing wrong here? Or may be this is not supposed to work at all. We have an internal only DNS server (dns1) with fake root zone. i.e a fake file for the zone ".