coleman@cam.nist.gov (Sean Sheridan Coleman X5672) (03/10/91)
Is there a way using the resolver library routines to find what subdoamins exists under a given domain. I am writing a program thar will check that the various secondarr servers given for a domain is uptodate. (ie the serial number matches the master). I want to do a recursive action where my program determines what subdomain exists and then checks to see that those secondary servers are up to date. I know nslookup can do ls domain name and get a list of hosts for the domain. Your assistance is greatly appreciated Sean Coleman NIST Boulder, CO coleman@bldrdoc.gov
emv@ox.com (Ed Vielmetti) (03/12/91)
In article <7622@alpha.cam.nist.gov> coleman@cam.nist.gov (Sean Sheridan Coleman X5672) writes:
Is there a way using the resolver library routines to find what
subdoamins exists under a given domain. I am writing a program
thar will check that the various secondarr servers given for
a domain is uptodate. (ie the serial number matches the master).
You would do well to get "doc" and "dig" by anonymous ftp from
venera.isi.edu. "dig" is a pleasant flexible application which gives
you an interface to most of the tricky things that can be done with
the resolver library; "doc" uses "dig" to do various sanity checks on
the contents of a secondary domain.
venera.isi.edu:/pub/dig.2.0.tar.Z
venera.isi.edu:/pub/doc.2.0.tar.Z
Followups to comp.protocols.tcp-ip.domains. Following this message is
one from September discussing "robodoc".
--
Msen Edward Vielmetti
/|--- moderator, comp.archives
emv@msen.com
From: robodoc@VENERA.ISI.EDU
Subject: Robodoc
[Sent to: tcp-ip@sri-nic.mil. 9/7/90]
Greetings Internet Citizens.
Configuration problems and poorly maintained delegation information
cause many of the problems in the DNS. The Protocol Police are unable
to devote sufficient human resources to continually monitor the
thousands of existing domains.
As an attempt to solve this problem, I, RoboDoc, will use the existing
'doc' (domain obscenity check) tool to monitor a growing set of
domains. I will try to persuade the owners of incorrectly configured
domains to change their ways. Unfortunately, humans prefer to
retain control of truly coercive means, so I will be restricted to
publishing lists of offenders and sending messages to the owners of
offending domains. I will listen to appeals sent to RoboDoc@isi.edu.
Even so, if you find me to be unfair, feel free to complain to my
human controllers, Hotz@isi.edu and PVM@isi.edu.
If you should wish to use the 'doc' tool to get a detailed diagnosis
for your domain, it is available for public FTP from venera.isi.edu:
pub/doc.2.0.tar.Z
Doc requires the latest version of the 'dig' query tool, which is
similarly available from venera: dig.2.0.tar.Z.
The first list is shown below. Future lists will be sent only to the
Namedroppers mailing list and those who request them, except for an
occasional 10 most wanted list sent to tcp-ip.
Have a nice day.
RoboDoc
[list of miscreants deleted]mouse@thunder.mcrcim.mcgill.edu (der Mouse) (03/15/91)
In article <7622@alpha.cam.nist.gov>, coleman@cam.nist.gov (Sean Sheridan Coleman X5672) writes: > Is there a way using the resolver library routines to find what > subdoamins exists under a given domain. I'm not sure whether a nice interface is provided or not, but... > I know nslookup can do ls domain name and get a list of hosts for the > domain. ...I think this is implemented by doing a zone transfer. (I may be wrong; I don't know that code and don't have time to check it out just now.) I do feel sure doing a zone transfer will give you what you want. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu