Re: Resolving RFC1918 addresses on recursive, caching servers

2017-11-09 Thread Greg Rivers
On Friday, November 10, 2017 10:27:53 Mark Andrews wrote: > Just slave the zones on the recursive servers. When you forward that server > does > all the recursion and returns the answer to you. If you do use forwarding > for RFC 1918 > zones use “forward only;” as you really don’t want talk to

Re: Resolving RFC1918 addresses on recursive, caching servers

2017-11-09 Thread Reindl Harald
Am 09.11.2017 um 23:34 schrieb Oscar Ricardo Silva: authoritative servers for all our in-addr.arpa domains and utexas.edu: - chisos.ots.utexas.edu (128.83.185.39) - glass.its.utexas.edu  (129.116.136.5) Some in-addr.arpa zones delegated to ns1.dept.utexas.edu on above authoritative servers:

Re: Resolving RFC1918 addresses on recursive, caching servers

2017-11-09 Thread Mark Andrews
Just slave the zones on the recursive servers. When you forward that server does all the recursion and returns the answer to you. If you do use forwarding for RFC 1918 zones use “forward only;” as you really don’t want talk to the AS112 servers. RFC 1918 reverse support really is easy. You s

Re: Resolving RFC1918 addresses on recursive, caching servers

2017-11-09 Thread Oscar Ricardo Silva
Some clarification: authoritative servers for all our in-addr.arpa domains and utexas.edu: - chisos.ots.utexas.edu (128.83.185.39) - glass.its.utexas.edu (129.116.136.5) Some in-addr.arpa zones delegated to ns1.dept.utexas.edu on above authoritative servers: 5.16.172.in-addr.arp

Resolving RFC1918 addresses on recursive, caching servers

2017-11-09 Thread Oscar Ricardo Silva
We use RFC1918 networks and have our authoritative servers configured to resolve for those networks. Some of these RFC1918 networks are delegated to departmental name servers. This has been running well (or apparently well) for several years but a few weeks ago one of our authoritative name se