Re: Resolve specified DNS name in a caching-only name server

2017-05-26 Thread Carl Byington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sat, 2017-05-27 at 09:11 +0800, Rui Mao wrote: > 1. Resolve test.a.com to 192.168.1.1 > 2. Still forward other *.a.com to outside DNS servers With bind, you have at least two choices. a) create test.a.com zone, so your server becomes authoritat

Re: Resolve specified DNS name in a caching-only name server

2017-05-26 Thread /dev/rob0
On Sat, May 27, 2017 at 09:11:23AM +0800, Rui Mao wrote: > I've set up a caching-only name server. But I'd like to know if it > can do following things. > > > > 1. Resolve test.a.com to 192.168.1.1 > > 2. Still forward other *.a.com to outside DNS servers You can make a zone of however many

Resolve specified DNS name in a caching-only name server

2017-05-26 Thread Rui Mao
Hi there, I've set up a caching-only name server. But I'd like to know if it can do following things. 1. Resolve test.a.com to 192.168.1.1 2. Still forward other *.a.com to outside DNS servers Best regards, Rui Mao ___ Please visit https

Re: bind-users Digest, Vol 2657, Issue 2

2017-05-26 Thread Chris Serella
The router doing something stupid (smart) sounds like it might be the right answer, I know that i had to open the port in the router and yes it does some intrusion detection etc so its possible. I know all outbound traffic is left alone and inbound is managed, i may see if i can turn off the f

Catalog "reconfig" calamity

2017-05-26 Thread /dev/rob0
I've started using the new catalog-zones feature, and whilst it has been pretty nice on one new server, it has been painful to implement on an existing one. I run three nameservers for a small F/OSS project, slackbuilds.org. One of these is a physical server machine, and the other two are virt