Is Split DNS on one server possible

[Kevin Darcy]

G. Roderick Singleton wrote:

> I have tried listen on with 8.2.2p5 and not had much success
> getting two named daemons functioning.
>
> One error is Dec  2 11:20:11 ns.pathtech.org named[12423]: Zone
> "home.pathtech.org" (file hosts.pathtech.internal): no NS RRs found at
> zone top

You need NS RR's in the master file for home.pathtech.org. I don't think this has
anything to do with your main problem though.

> Yet I have a proper in-addr file.

Shouldn't have any bearing on either problem.

> I also get
> Dec  2 11:26:38 ns.pathtech.org named[12436]: There may be a name server
> already running on [192.168.32.10].1053
> Dec  2 11:26:38 ns.pathtech.org named[12436]: deleting interface
> [192.168.32.10].1053
> Dec  2 11:26:38 ns.pathtech.org named[12436]: deleting interface
> [192.168.32.10].1053
> Dec  2 11:26:38 ns.pathtech.org named[12436]: not listening on any
> interfaces
> Dec  2 11:26:38 ns.pathtech.org named[12436]: not listening on any
> interfaces
>
> in my named.conf.internal, I have specified as follows:
> options {
>         directory "/etc/dns";
>         forwarders{ 1.2.3.4; };
>
>  listen-on port 1053 { 192.168.32/24; };
> }

Hmmm... I must admit I've never used an address prefix in a listen-on statement
before, and therefore can't personally vouch for its functionality. What happens if
you explicitly specify the address, i.e. 192.168.32.10?

Also, are you sure you have nothing else listening on port 1053? That's not in the
reserved range, so in theory any other process could grab it. Do a "netstat" while
all named's are down and see if anything is listening on the port. Assuming you see
a listener, if you have a copy of the "lsof" utility, maybe you can track it back
easily to a particular process. Or, just use the laborious
start-bringing-down-services-until-the-listener-disappears method.

Also, when you get this working, you may need to pay attention to pid files and/or
ndc channels (so that the named's don't stomp on each other).


- Kevin