Charles Butcher writes:
> > | From: Egotists Anonymous (koreth @
> > | Subject: And the Funky Hostname Award for this week goes to:
> > |
> > | 129_179_75_12.cdc.com
> > |
> > | Now, I've heard of uncreative host naming, but that's ridiculous.
> Pity the poor buggers who have to update all the references to this host
> when it moves to another network.... and it _will_
If the host becomes 18.104.22.168, I suppose the outside will see it as
When I get a LOT of time, one of the bind hacks I have been thinking of is
to add a new named.boot command with a syntax something like
cloak 22.214.171.124 ncr.com.
This would effectively load bogus but "correct" A and PTR records for all
hosts on the 126.96.36.199 network without having to generate a named.hosts
and named.rev. A PTR query on 188.8.131.52.in-addr.arpa returns
h150-150-150-150.ncr.com. An A query on h150-150-150-150.ncr.com would
return, of course, 184.108.40.206. Very useful for a "complete" external
DNS that should make any FTP site that does reverse lookups happy and at the
same time not give out useful information to the outside.
The implementation would not really load all of the RR's into the cache.
Real entries in named.hosts and named.rev should override the generated
RR's. From discussions I've had with people, it seems doable. Has anyone
actually tried anything like this?
Greg Nenych <greg .
AT&T Global Information Solutions Canada Ltd.
6865 Century Ave, Mississauga, Ontario, Canada, L5N 2E2