Adding sud domain PTR record using DNSCMD?

Claude Lachapelle

I need to bulky adds PTR records under a reverse lookup zone which contain
sub domains:

10.100.in-addr-arpa
- 100
- 2
- 200
- 3
- 300

I tried:

/recordadd 100.10.100.in-addr.arpa 250 ptr record.domain.ca

but I'm getting

Command failed: DNS_ERROR_ZONE_DOES_NOT_EXIST 9601 (00002581)

I understand that I should specify 10.100.in-addr.arpa for the zone, but how
to specify the domain where I want to add the record???

Thanks.

Claude Lachapelle
Systems Administrator, MCSE

Chris Dent [MVP]

Hi Claude,

All records are created relative to the zone. So the record has to be
250.100 to make 250.100.10.100.in-addr.arpa (for the IP 100.10.100.250).

dnscmd /RecordAdd 10.100.in-addr.arpa. 250.100 PTR record.domain.ca

If you actually have a zone for 10.100.x.x Subnet the zone name is
100.10.in-addr.arpa, and you would add 250.100 to that to make the entry for
10.100.100.250. Just in case it's really a private zone for a private IP
range rather than a public one

HTH

--
Chris Dent
MVP - Directory Services


"Claude Lachapelle" <ClaudeLachapelle@discussions.microsoft.com> wrote in
message news:E96FA627-A267-4477-B7D6-BF2E62C8A9A2@microsoft.com...
>I need to bulky adds PTR records under a reverse lookup zone which contain
> sub domains:
>
> 10.100.in-addr-arpa
> - 100
> - 2
> - 200
> - 3
> - 300
>
> I tried:
>
> /recordadd 100.10.100.in-addr.arpa 250 ptr record.domain.ca
>
> but I'm getting
>
> Command failed: DNS_ERROR_ZONE_DOES_NOT_EXIST 9601 (00002581)
>
> I understand that I should specify 10.100.in-addr.arpa for the zone, but
> how
> to specify the domain where I want to add the record???
>
> Thanks.
>
> Claude Lachapelle
> Systems Administrator, MCSE

Claude Lachapelle

Thanks!

Now I'm looking for a way to create those sub domain records automatically
with dnscmd... since they are not zone, which kind of record they are?

Usage: DnsCmd <ServerName> /RecordAdd <Zone> <NodeName> [/Aging] [/OpenAcl]
[<Ttl>] <RRType> <RRData>

<RRType> <RRData>
A <IPAddress>
NS,CNAME,MB,MD <HostName|DomainName>
PTR,MF,MG,MR <HostName|DomainName>
MX,RT,AFSDB <Preference> <ServerName>
SRV <Priority> <Weight> <Port> <HostName>
SOA <PrimaryServer> <AdminEmail> <Serial#>
<Refresh> <Retry> <Expire> <MinTTL>
AAAA <Ipv6Address>
TXT <String> [<String>]
X25,HINFO,ISDN <String> [<String>]
MINFO,RP <MailboxName> <ErrMailboxName>
WKS <Protocol> <IPAddress> <Service> [<Service>]..]
KEY <Flags> <KeyProtocol> <CryptoAlgorithm> <Base64Data>
SIG <TypeCovered> <CryptoAlgorithm> <LabelCount>
<OriginalTTL> <SigExpiration> <SigInception>
<KeyTag> <Signer's Name> <Base64Data>
NXT <NextName> <Type> [<Type>...]
WINS <MapFlag> <LookupTimeout>
<CacheTimeout> <IPAddress> [<IPAddress>]
WINSR <MapFlag> <LookupTimeout>
<CacheTimeout> <RstDomainName>
<Zone> -- <ZoneName> | /RootHints
<ZoneName> -- FQDN of a zone
<NodeName> -- name of node for which a record will be added
- FQDN of a node (name with a '.' at the end) OR
- node name relative to the ZoneName OR
- "@" for zone root node OR
- service name for SRV only (e.g. _ftp._tcp)
<Ttl> -- TTL for the RR (Default: TTL defined in SOA)
<HostName> -- FQDN of a host
<IPAddress> -- e.g. 255.255.255.255
<ipv6Address> -- e.g. 1:2:3:4:5:6:7:8
<Protocol> -- UDP | TCP
<Service> -- e.g. domain, smtp
<TypeCovered> -- type of the RRset signed by this SIG
<CryptoAlgorithm> -- 1=RSA/MD5, 2=Diffie-Hellman, 3=DSA
<SigExpiration> -- yyyymmddhhmmss - GMT
<SigInception> -- yyyymmddhhmmss - GMT
<KeyTag> -- used to discriminate between multiple SIGs
<Signer's Name> -- domain name of signer
<KeyProtocol> -- 1=TLS, 2=email, 3=DNSSEC, 4=IPSEC
<Base64Data> -- KEY or SIG binary data in base64 notation
<NextName> -- domain name of next RRSet in zone
"Chris Dent [MVP]" wrote:

>
> Hi Claude,
>
> All records are created relative to the zone. So the record has to be
> 250.100 to make 250.100.10.100.in-addr.arpa (for the IP 100.10.100.250).
>
> dnscmd /RecordAdd 10.100.in-addr.arpa. 250.100 PTR record.domain.ca
>
> If you actually have a zone for 10.100.x.x Subnet the zone name is
> 100.10.in-addr.arpa, and you would add 250.100 to that to make the entry for
> 10.100.100.250. Just in case it's really a private zone for a private IP
> range rather than a public one
>
> HTH
>
> --
> Chris Dent
> MVP - Directory Services
>
>
> "Claude Lachapelle" <ClaudeLachapelle@discussions.microsoft.com> wrote in
> message news:E96FA627-A267-4477-B7D6-BF2E62C8A9A2@microsoft.com...
> >I need to bulky adds PTR records under a reverse lookup zone which contain
> > sub domains:
> >
> > 10.100.in-addr-arpa
> > - 100
> > - 2
> > - 200
> > - 3
> > - 300
> >
> > I tried:
> >
> > /recordadd 100.10.100.in-addr.arpa 250 ptr record.domain.ca
> >
> > but I'm getting
> >
> > Command failed: DNS_ERROR_ZONE_DOES_NOT_EXIST 9601 (00002581)
> >
> > I understand that I should specify 10.100.in-addr.arpa for the zone, but
> > how
> > to specify the domain where I want to add the record???
> >
> > Thanks.
> >
> > Claude Lachapelle
> > Systems Administrator, MCSE
>

Claude Lachapelle

When adding a PTR record into this kind of zone, if the zone does not exist,
it is automatically created - beautiful...

"Claude Lachapelle" wrote:

> Thanks!
>
> Now I'm looking for a way to create those sub domain records automatically
> with dnscmd... since they are not zone, which kind of record they are?
>
> Usage: DnsCmd <ServerName> /RecordAdd <Zone> <NodeName> [/Aging] [/OpenAcl]
> [<Ttl>] <RRType> <RRData>
>
> <RRType> <RRData>
> A <IPAddress>
> NS,CNAME,MB,MD <HostName|DomainName>
> PTR,MF,MG,MR <HostName|DomainName>
> MX,RT,AFSDB <Preference> <ServerName>
> SRV <Priority> <Weight> <Port> <HostName>
> SOA <PrimaryServer> <AdminEmail> <Serial#>
> <Refresh> <Retry> <Expire> <MinTTL>
> AAAA <Ipv6Address>
> TXT <String> [<String>]
> X25,HINFO,ISDN <String> [<String>]
> MINFO,RP <MailboxName> <ErrMailboxName>
> WKS <Protocol> <IPAddress> <Service> [<Service>]..]
> KEY <Flags> <KeyProtocol> <CryptoAlgorithm> <Base64Data>
> SIG <TypeCovered> <CryptoAlgorithm> <LabelCount>
> <OriginalTTL> <SigExpiration> <SigInception>
> <KeyTag> <Signer's Name> <Base64Data>
> NXT <NextName> <Type> [<Type>...]
> WINS <MapFlag> <LookupTimeout>
> <CacheTimeout> <IPAddress> [<IPAddress>]
> WINSR <MapFlag> <LookupTimeout>
> <CacheTimeout> <RstDomainName>
> <Zone> -- <ZoneName> | /RootHints
> <ZoneName> -- FQDN of a zone
> <NodeName> -- name of node for which a record will be added
> - FQDN of a node (name with a '.' at the end) OR
> - node name relative to the ZoneName OR
> - "@" for zone root node OR
> - service name for SRV only (e.g. _ftp._tcp)
> <Ttl> -- TTL for the RR (Default: TTL defined in SOA)
> <HostName> -- FQDN of a host
> <IPAddress> -- e.g. 255.255.255.255
> <ipv6Address> -- e.g. 1:2:3:4:5:6:7:8
> <Protocol> -- UDP | TCP
> <Service> -- e.g. domain, smtp
> <TypeCovered> -- type of the RRset signed by this SIG
> <CryptoAlgorithm> -- 1=RSA/MD5, 2=Diffie-Hellman, 3=DSA
> <SigExpiration> -- yyyymmddhhmmss - GMT
> <SigInception> -- yyyymmddhhmmss - GMT
> <KeyTag> -- used to discriminate between multiple SIGs
> <Signer's Name> -- domain name of signer
> <KeyProtocol> -- 1=TLS, 2=email, 3=DNSSEC, 4=IPSEC
> <Base64Data> -- KEY or SIG binary data in base64 notation
> <NextName> -- domain name of next RRSet in zone
> "Chris Dent [MVP]" wrote:
>
> >
> > Hi Claude,
> >
> > All records are created relative to the zone. So the record has to be
> > 250.100 to make 250.100.10.100.in-addr.arpa (for the IP 100.10.100.250).
> >
> > dnscmd /RecordAdd 10.100.in-addr.arpa. 250.100 PTR record.domain.ca
> >
> > If you actually have a zone for 10.100.x.x Subnet the zone name is
> > 100.10.in-addr.arpa, and you would add 250.100 to that to make the entry for
> > 10.100.100.250. Just in case it's really a private zone for a private IP
> > range rather than a public one
> >
> > HTH
> >
> > --
> > Chris Dent
> > MVP - Directory Services
> >
> >
> > "Claude Lachapelle" <ClaudeLachapelle@discussions.microsoft.com> wrote in
> > message news:E96FA627-A267-4477-B7D6-BF2E62C8A9A2@microsoft.com...
> > >I need to bulky adds PTR records under a reverse lookup zone which contain
> > > sub domains:
> > >
> > > 10.100.in-addr-arpa
> > > - 100
> > > - 2
> > > - 200
> > > - 3
> > > - 300
> > >
> > > I tried:
> > >
> > > /recordadd 100.10.100.in-addr.arpa 250 ptr record.domain.ca
> > >
> > > but I'm getting
> > >
> > > Command failed: DNS_ERROR_ZONE_DOES_NOT_EXIST 9601 (00002581)
> > >
> > > I understand that I should specify 10.100.in-addr.arpa for the zone, but
> > > how
> > > to specify the domain where I want to add the record???
> > >
> > > Thanks.
> > >
> > > Claude Lachapelle
> > > Systems Administrator, MCSE
> >