private address 192.168.x.x or 10.x.x.x on a public dns

[Baird, Josh]

The correct way to handle RFC1918 space in DNS is to use "split brain"
DNS.  Using BIND's views you will be able to configure two different
views for the zones, one view that will respond to internal queries
(which will return the private IP), and another view that will respond
to external queries (using the public IP).

Josh

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of roger
Sent: Friday, April 25, 2008 3:40 AM
To: comp-protocols-dns-bind at isc.org
Subject: private address 192.168.x.x or 10.x.x.x on a public dns

Hello,

I am trying to find some information that I already believe to be
true.

I belive: You shouldn't configure a DNS, that answers queries to the
internet, with a host that will point to a private address.


Our engineering department wants me to do the following:

host      IN       A     192.168.99.154

on a nameserver that answers queries to the internet.


I feel this is wrong, I think this is not allowed, but I can not find
the RFC, book, internet article that will support my claim. My google-
foo has failed me. Can anyone lend a helping hand, or if someone can
lead me to documentation that says it is ok to do so would also be
helpful.

Best Regards,
Roger Murray