something like "forwarders" in bind for tinydns

[cr lankis]

Hi,

This is not a technical question, is more a design question.

I work for a small hosting provider, they have primary and seconday
DNS servers running bind and some other servers running control panels
like plesk/ensim/cPanel with their own DNS server.

On the current configuration bind resolves all the requests and as
"forwarders" it has the IPs of the control panels, so it resolves all
the domains that it has and the ones in the control panels.

I want to move from bind to tinydns and resolve just the domains that
we are hosting, but not all of them are in the same server, the ones
on the control panels as well.

Is there any configuration like "forwarders" on bind for tinydns? If
one of the "forwarders" has the domain, it resolves it, if they don't,
it does not resolve.

Any recommendation on the design is more than welcome.

Thanks,

CR

[Matthew Dempsky]

Post by cr lankis
Is there any configuration like "forwarders" on bind for tinydns?

No, tinydns only supports answering queries from its data file.

Post by cr lankis
Any recommendation on the design is more than welcome.

If your control panel DNS servers support AXFR, then you can script a
cron job to do an AXFR transfer using axfr-get every few minutes.
Then concatenate the fetched files into a single data file, and feed
it to tinydns-data.

[cr lankis]

Thanks for you answer.

Post by Matthew Dempsky

Post by cr lankis
Any recommendation on the design is more than welcome.

If your control panel DNS servers support AXFR, then you can script a
cron job to do an AXFR transfer using axfr-get every few minutes.
Then concatenate the fetched files into a single data file, and feed
it to tinydns-data.

The problem here is that I don't know the domains, each server has
hundreds of domains and they change everyday.

[Paul Jarc]

Post by cr lankis
On the current configuration bind resolves all the requests and as
"forwarders" it has the IPs of the control panels, so it resolves all
the domains that it has and the ones in the control panels.

If you can rearrange your names so that each control panel gets its
own subdomain, you could have tinydns delegate those subdomains.


paul