NSLOOKUP SRV Record Output - IP address necessary?
- From: "bmack500" <brett.mack@xxxxxxxxx>
- Date: 14 Jul 2005 11:31:09 -0700
We have a Non-MS DNS implementation. We supposedly have DDNS enabled &
functioning, however I've discovered things which I am not sure have an
effect. Suppose we do the following query, with it's associated output:
***************************************************************************
C:\nslookup
Default Server: dc1.example.microsoft.com
Address: 10.0.0.14
set type=srv
_ldap._tcp.dc._msdcs.example.microsoft.com
Server: dc1.example.microsoft.com
Address: 10.0.0.14
_ldap._tcp.dc._msdcs.example.microsoft.com SRV service location:
priority = 0
weight = 0
port = 389
svr hostname = dc1.example.microsoft.com
_ldap._tcp.dc._msdcs.example.microsoft.com SRV service location:
priority = 0
weight = 0
port = 389
svr hostname = dc2.example.microsoft.com
dc1.example.microsoft.com internet address = 10.0.0.14
dc2.example.microsoft.com internet address = 10.0.0.15
***************************************************************************
Many of our SRV records are missing the last part - the Host name
followed by the internet address. For the same record, some of them are
there and some aren't.
Reading the RFC, it looks as though this is optional. However, what is
Microsoft's view on this? Does it break things if the target record is
present, the a record for the target exists in DNS, but an SRV query
does not return the address?
.
- Follow-Ups:
- Re: NSLOOKUP SRV Record Output - IP address necessary?
- From: Steve Duff [MVP]
- Re: NSLOOKUP SRV Record Output - IP address necessary?
- Prev by Date: DHCP and DNS problems 2003
- Next by Date: ~Root hints issue
- Previous by thread: DHCP and DNS problems 2003
- Next by thread: Re: NSLOOKUP SRV Record Output - IP address necessary?
- Index(es):