Verification of SRV records through dig or nslookup
Kevin Darcy
kcd at daimlerchrysler.com
Thu Oct 17 18:08:26 UTC 2002
Thomas Renzy wrote:
> All,
>
> I've set up DNS to allow updates of SRV records to my DNS server in a lab
> from an Active Directory environment. I see them below by looking directly
> at the file
>
> cat db.veritas.com
> <SNIP>
> $ORIGIN _tcp.veritas.com.
> _kpasswd 600 IN SRV 0 100 464
> svladr01-lab.veritas.com. ;Cl=2
> 600 IN SRV 0 100 464 svladr02-lab.veritas.com.
> ;Cl=2
> _ldap 600 IN SRV 0 100 389 svladr01-lab.veritas.com.
> ;Cl=2
> 600 IN SRV 0 100 389 svladr02-lab.veritas.com.
> ;Cl=2
> _gc 600 IN SRV 0 100 3268 svladr01-lab.veritas.com.
> ;Cl=2
> _kerberos 600 IN SRV 0 100 88
> svladr01-lab.veritas.com. ;Cl=2
> 600 IN SRV 0 100 88 svladr02-lab.veritas.com.
> ;Cl=2
> $ORIGIN _udp.veritas.com.
> _kpasswd 600 IN SRV 0 100 464
> svladr01-lab.veritas.com. ;Cl=2
> 600 IN SRV 0 100 464 svladr02-lab.veritas.com.
> ;Cl=2
> _kerberos 600 IN SRV 0 100 88
> svladr01-lab.veritas.com. ;Cl=2
> 600 IN SRV 0 100 88 svladr02-lab.veritas.com.
> ;Cl=2
> <SNIP>
>
> How do I check them using dig or nslookup? I've tried using dig @localhost
> srv _kpasswd_tcp.veritas.com.
> but to no avail. What is the correct way to check that the SRV records have
> been updated in DNS?
Try looking up the name _kpasswd._tcp.veritas.com (you were missing a dot).
- Kevin
More information about the bind-users
mailing list