Re: redirecting root hints to fake internal root server

name.com is not 192.168.1.1.   Colin   From: Colin Harvey To: "wbr...@e1b.org" Cc: "bind-users-bounces+wbrown=e1b@lists.isc.org" ; bind users Sent: Tuesday, August 27, 2013 2:13 PM Subject: Re: redirecting root hints to fake internal root server Thanks.  But

Re: redirecting root hints to fake internal root server

Thanks.  But I already have that option for the internal.hostname.com zone.  Still not seeing traffic going to 192.168.1.1.   Colin From: "wbr...@e1b.org" To: Colin Harvey Cc: bind users ; bind-users-bounces+wbrown=e1b@lists.isc.org Sent: Tuesday, August 27, 2013 1:20 PM S

redirecting root hints to fake internal root server

  My environment is firewalled from the real world.  For queries on zones to which I'm not master, I want to recurse to a corporate server.  nslookup some.internal.hostname.com internal.corporate.server works fine.  Setting "." to use this internal server in the root.hints file does not.  In fac

named.ca

  We're running BIND 9.6.1-P3 on several machines setup to be forwarders.  Some domains are not resolvable via the forwarder, so named.ca has those domains listed with the appropriate nameservers to reach to resolve the requests.   For some reason, one host is either not using its named.ca or has