Getting hold of serial numbers

[Treptow, Craig]

Query for the SOA record of the zone in question:

C:\>dig @206.195.197.10 principal.com soa

; <<>> DiG 9.2.4 <<>> @206.195.197.10 principal.com soa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 793
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0

;; QUESTION SECTION:
;principal.com.                 IN      SOA

;; ANSWER SECTION:
principal.com.          3600    IN      SOA     ns1.principal.com. =
dns.principal.com. 2004121400 21600 3600 1728000 3600


;; AUTHORITY SECTION:
principal.com.          3600    IN      NS      =
cmtu.mt.ns.els-gms.att.net.
principal.com.          3600    IN      NS      auth02.ns.uu.net.
principal.com.          3600    IN      NS      auth20.ns.wcom.com.
principal.com.          3600    IN      NS      =
cbru.br.ns.els-gms.att.net.

;; Query time: 10 msec
;; SERVER: 206.195.197.10#53(206.195.197.10)
;; WHEN: Wed Dec 15 16:42:08 2004
;; MSG SIZE  rcvd: 193


>-----Original Message-----
>From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
>Behalf Of D McDonald
>Sent: Wednesday, December 15, 2004 4:36 PM
>To: bind-users at isc.org
>Subject: Getting hold of serial numbers
>
>
>Earlier today Stephen noticed that the serial numbers on the=20
>zone files=20
>didnt match between my dns server, and thouse of att. How do=20
>you go about=20
>finding out the serial number of zone files? How would you do=20
>this from a=20
>*nix command line?
>
>Renski
>
> --=20
>renski at sdf.lonestar.org
>SDF Public Access UNIX System - http://sdf.lonestar.org
>
>
>


-----Message=20Disclaimer-----

This=20e-mail=20message=20is=20intended=20only=20for=20the=20use=20of=20the=20individual=20or
entity=20to=20which=20it=20is=20addressed,=20and=20may=20contain=20information=20that=20is
privileged,=20confidential=20and=20exempt=20from=20disclosure=20under=20applicable=20law.
If=20you=20are=20not=20the=20intended=20recipient,=20any=20dissemination,=20distribution=20or
copying=20of=20this=20communication=20is=20strictly=20prohibited.=20If=20you=20have
received=20this=20communication=20in=20error,=20please=20notify=20us=20immediately=20by
reply=20email=20to=20Connect at principal.com=20and=20delete=20or=20destroy=20all=20copies=20of
the=20original=20message=20and=20attachments=20thereto.=20Email=20sent=20to=20or=20from=20the
Principal=20Financial=20Group=20or=20any=20of=20its=20member=20companies=20may=20be=20retained
as=20required=20by=20law=20or=20regulation.

Nothing=20in=20this=20message=20is=20intended=20to=20constitute=20an=20Electronic=20signature
for=20purposes=20of=20the=20Uniform=20Electronic=20Transactions=20Act=20(UETA)=20or=20the
Electronic=20Signatures=20in=20Global=20and=20National=20Commerce=20Act=20("E-Sign")
unless=20a=20specific=20statement=20to=20the=20contrary=20is=20included=20in=20this=20message.