Right. However the common solution is to delegate a small subdomain just for the 3dns'ed RR's to it (and perhaps cname to them from the top level).
I figured. And also considered the sub-delegation. Only one problem. More often than not the website "www.domain.com" also wants "domain.com" pointing to their service. If you point it all at the 3DNS, that kind of blows the sub-delegation theory. AND, if you sub-delegate the "www.domain.com" and put an entry in the domain.com zone record on your regular DNS server - it can be managed OK for a few domains, but what about when you have a very large server farm... [eyes rolling] gads!
Yep, its a hacked up bind8. Haven't taken the time to pull it apart as much as I'd like, but I would be surprised if anything you could do with ~8.1 didn't work with their box.
We should all hammer on Vixie or ISC to get this in BIND anyways. Wouldn't that be sweet and save us all $30-40k per device.... -----Original Message----- From: kevin graham [mailto:kgraham@dotnetdotcom.org] Sent: Thursday, July 06, 2000 9:31 AM To: Karyn Ulriksen Cc: 'Ted Mektrakarn'; 'nanog@merit.edu' Subject: RE: LoadBalancing products: Foundry ServerIron
It seems from what I have read that 3DNS wants to do all DNS for the domain zone including MX, CNAMEs, etc.
Right. However the common solution is to delegate a small subdomain just for the 3dns'ed RR's to it (and perhaps cname to them from the top level).
Do you know if it supports SRV records (Windows 2000 machines managed by ADS are happier when they can manage these records), ACLs for the zone record IXFRs from the 2000 machines, etc? Are the running some modified version of BIND to accomodate this?
Yep, its a hacked up bind8. Haven't taken the time to pull it apart as much as I'd like, but I would be surprised if anything you could do with ~8.1 didn't work with their box. ..kg..