[BlueOnyx:18157] Re: Changes in DNS logs since recent updates

[blueonyxuser at gmail.com]

> Depends. So you run a VPN on BlueOnyx? And clients that connect via that
VPN
> get addresses from the 192.168.0.0/16 address range assigned?
> 
> In that case: "Server Management" / "DNS" / "Edit Primary Services".
> >From the pulldown "Add Record ..." select "Reverse Address (PTR) Record".
> 
> Ipaddr: 192.168.0.0
> Netmask: 255.255.0.0
> Hostname: vpn (or whatever you want)
> Domain: server-name.com (whatever you like)
> 
> That creates the 168.192.in-addr.arpa zone in your DNS that Carl
mentioned. You
> could then populate with A Records if you'd like, but that's probably not
needed.

Thanks for the quick response.

I should have clarified the VPN aspect ( in case it affects the solution ) -
I use BO as a server appliance with a NIC on the 192.168.0.x/24 as the WAN
side servicing only WWW traffic for the data from the VPN and
192.168.10.x/24 as the LAN side. On the LAN side I have a Cisco from a
wireless/phone carrier provider forwarding 192.168.20.x through to
192.168.254.x on to the 192.168.10.x/24 LAN segment.

All the traffic from the VPN therefore either talks VPN to VPN or points at
the BO server on 192.168.10.x and then for anything that wants out to the
internet it must pass through either the SMTP on the BO or use the TCP/UDP
forwarders running on the BO ( to deliberately limit VPN traffic to the
Internet ).

So essentially I need to cover 192.168.20.x through to 192.168.254.x within
the BO but not the whole 192.168/16 - which makes it difficult I think.

Does this make sense?

Tony