26 Jul
2006
26 Jul
'06
5:13 p.m.
Steve Blair wrote:
Klaus Darilion wrote:
Why so complicated? Just use grep and dig.
regards
klaus
Steve Blair wrote:
Possible. I have a test scheduled today with our DNS "person".During
that session they will enable logging, it is usually off. Hopefully the
logging will explain what is happening. Klaus Darilion wrote:
maybe someone fumbled in DNS? :-)
Use ngrep to watch also the DNS lookups (ngrep port 5060 or port 53)
and verify what ser really looks up in DNS. The kerberos SRV entries
must not interfere, but they are in a different domain, thus when
looking up _sip._udp.... the kerberos entries should never be seen
by ser.
OK. I'll add this check. I agree the kerberos entries shouldn't
interfere but I cannot explain why SER would think the domain
controller host would be the next hop.