DNS won't resolve SRV records with recursion disabled
I have DNS installed on a Windows Server 2008 R2 server. I have a standard zone created (no AD integration). I have recursion disabled. When I use NSLookup to lookup any of the A records or CName Records the results are returned as
expected. However, if I attempt to lookup any SRV or MX Records, the list of root hints are returned (which is what I would expect if I was attempting to lookup a domain not hosted on this server). Now I enable recursion and run the same exact
commands and I get the results I'm expecting.
I'm stumped.....
DB
Reader's digest version: Putting a period at the end of my record, resolved the issue. This seems to be a difference between Windows 2003 and Windows 2008R2
Long version:
Thanks for the debug tip. That confirms the issue. So to backup a little, I had a Windows 2003 box running DNS. I planned on decommissioning this box; therefore, I stood up the second server, made a secondary DNS zone, once all records
transferred, I flipped the primary and secondary roles.
The real problem is this zone cannot find any of the TXT records such as SRV and MX. When I run NSLookup with recursion disabled, my results are:
HEADER:
opcode = QUERY, id = 18, rcode = NOERROR
header flags: response, want recursion
questions = 1, answers = 0, authority records = 13, additional = 3
That makes perfect sense why recursion is working. If I run the same results on the secondary DNS server (the original server) the results are expected:
HEADER:
opcode = QUERY, id = 20, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 4, authority records = 0, additional = 4
SO THE REAL QUESTION is why can't the new server find these records, especially since it's a copy of the zone from the old server. I flipped the servers back, deleted the DNS zone (and files) on the new server, restarted DNS service, created the zone
again, and allowed the content to copy over from the old server and I STILL get the same results.
The last thing I did was created a new SRV record on the new server and performed another NSLookup, but still get the same results.
So then I remembered
MuhammadUmar's post about putting a period at the end of my nslookup command. I honestly didn't that that was going to change the results, but BAM. I was wrong. When I put in the request with a period at the end of the record, I get the
results I'm expecting.
Thanks all for helping me on this one!
DB
Similar Messages
-
guys,
i googled, read the DNS & BIND book (very useful), but still haven't solved my problem and this is killing me as i have spent days and the darn thing simply refuses to work!!! i am desperate and need your help.
i am trying to set up a DNS server on my dual NIC x86 Solaris 10.
1. i am getting confused with naming interfaces. i seem cannot have two network ifaces named like m1.example.com. each one must have its own unique name, right? [pls advise here]
so i name them m1.example.com and m2.example.com respectively. m1 is for router and m2 is for switch (LAN).
m1.example.com - 10.0.0.2
m2.example.com - 192.168.16.1
2. secondly I cannot get the SOA record. what interface should be used as SOA?? i tried m1 as it is "primary" (iprb0) and connects to the internet. however, it didn't work.
i even tried m3.example.com trying to combine two interfaces as below (still won't work):
my db files (excerps, server is down, writing from home) :
DB.EXAMPLE.COM
$TTL 3h
@ IN SOA m3.example.com. admin.example.com. ( 1 3h 1h 1w 1h)
IN NS m3.example.com.
localhost IN A 127.0.0.1
m1.example.com IN A 10.0.0.2
m2.example.com IN A 192.168.16.1
example.com IN MX 10 m3.example.com
m3 IN A 10.0.0.2
IN A 192.168.16.1
DB.10.0.0$TTL 3h
@ IN SOA m3.example.com. admin.example.com. ( 1 3h 1h 1w 1h)
IN NS m3.example.com.
1 IN PTR m3.example.com
DB.192.168.16$TTL 3h
@ IN SOA m3.example.com. admin.example.com. ( 1 3h 1h 1w 1h)
IN NS m3.example.com.
2 IN PTR m3.example.com
DB.127.0.0$TTL 3h
@ IN SOA m3.example.com. admin.example.com. ( 1 3h 1h 1w 1h)
IN NS m3.example.com.
1 IN PTR localhost.the previuous incarnation of the files contained m1 instead of m3 as SOA and NS, but like i mentioned already, it didn't work either.
i am able to ping router 10.0.0.1, but can't surf.
when i nslookup m3.example.com it gives:
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: m3.example.com
Address: 10.0.0.2
Name: m3.example.com
Address: 192.168.16.1and if i nslookup m1.example.com and m2.example.com it gives proper addresses (10.0.0.2 and 192.168.16.1 respectively).
DNS is running and files don't return errors after named-checkzone.
the idea is to make DNS server work for local network (192.168.16/24) and install postfix on top. however i am stuck with DNS at the moment.
please, anybody point me in the right direction - need to get this working by tomorrow!!!!!
many thanks for your replies.Whats your named.conf look like? Also, google DNS forwarder/forwarding....
Tom de -
in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adaptersHi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
the latest run of that...
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
Starting test: DNS
See DNS test in enterprise tests section for results
......................... CM-DC-NY01 passed test DNS
See DNS test in enterprise tests section for results
......................... CM-DC1-NY01 passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : cmedia
Starting test: CheckSDRefDom
......................... cmedia passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... cmedia passed test CrossRefValidation
Running enterprise tests on : cmedia.local
Starting test: DNS
Test results for domain controllers:
DC: cm-dc-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.6
DNS servers:
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
192.168.200.5 (CM-DC1-NY01) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
Matching CNAME record found at DNS server 192.168.200.6:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.pdc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.5:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.pdc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
DC: CM-DC1-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000010] Microsoft Hyper-V Network Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.5, 0000::0000:0000:0000:0000
DNS servers:
192.168.200.5 (CM-DC1-NY01) [Valid]
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 198.32.64.12 (l.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12 [Err
or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:1::803f:235 [Error details: 1460 (Type: Win32 - Description: This operation ret
urned because the timeout period expired.)]
DNS server: 2001:500:2::c (c.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2::c [Error details: 1460 (Type: Win32 - Description: This operation returned b
ecause the timeout period expired.)]
DNS server: 2001:500:2d::d (d.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2d::d [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:84::b (b.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:84::b [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:ba3e::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retu
rned because the timeout period expired.)]
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:c27::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retur
ned because the timeout period expired.)]
DNS server: 2001:7fd::1 (k.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fd::1 [Error details: 1460 (Type: Win32 - Description: This operation returned bec
ause the timeout period expired.)]
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 128.9.0.107 (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2f::f [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:3::42 [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fe::53 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:dc3::35 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 128.63.2.53 (h.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.112.36.4 (g.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.168.200.5 (CM-DC1-NY01)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.cmedia.local. is operational on IP 192.168.200.6
DNS server: 192.203.230.10 (e.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.228.79.201 (b.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.33.4.12 (c.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.36.148.17 (i.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.5.5.241 (f.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.58.128.30 (j.root-servers.net.)
All tests passed on this DNS server
DNS server: 193.0.14.129 (k.root-servers.net.)
All tests passed on this DNS server
DNS server: 198.41.0.4 (a.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.83.42 (l.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.91.13 (d.root-servers.net.)
All tests passed on this DNS server
DNS server: 202.12.27.33 (m.root-servers.net.)
All tests passed on this DNS server
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: cmedia.local
cm-dc-NY01 PASS PASS PASS PASS PASS WARN n/a
CM-DC1-NY01 PASS PASS PASS PASS PASS WARN n/a
......................... cmedia.local passed test DNS
Starting test: LocatorCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test LocatorCheck
Starting test: FsmoCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test FsmoCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
provided.
......................... cmedia.local passed test Intersite -
I am having problem for srv record creation in outlook autodiscovery, I am using cloudflare for external DNS all is fine but connectivity test saying
Attempting to locate SRV record _autodiscover._tcp.tulisoft.co.in in DNS.
The Autodiscover SRV record wasn't found in DNS "
My cloudflare settings as follows,
Service:_autodiscover
Protocol:tcp
Name:@
Priority:0
Weight:0
Port:443
Target:HOSTING.tulisoft.co.in
please let me know any mistake
Thanks
ParthaNow another error, Its exchange 2013
Test Details
Test Details
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
Testing Autodiscover failed.
Additional Details
Elapsed Time: 44430 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 44429 ms.
Test Steps
Attempting to test potential Autodiscover URL https://tulisoft.co.in/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 42136 ms.
Test Steps
Attempting to resolve the host name tulisoft.co.in in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 108.162.196.193, 108.162.197.193
Elapsed Time: 56 ms.
Testing TCP port 443 on host tulisoft.co.in to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 42079 ms.
Attempting to test potential Autodiscover URL https://autodiscover.tulisoft.co.in/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 970 ms.
Test Steps
Attempting to resolve the host name autodiscover.tulisoft.co.in in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 138.91.37.102
Elapsed Time: 89 ms.
Testing TCP port 443 on host autodiscover.tulisoft.co.in to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 231 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 649 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.tulisoft.co.in on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=HOSTING, Issuer: CN=HOSTING.
Elapsed Time: 626 ms.
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name autodiscover.tulisoft.co.in doesn't match any name found on the server certificate CN=HOSTING.
Elapsed Time: 0 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 646 ms.
Test Steps
Attempting to resolve the host name autodiscover.tulisoft.co.in in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 138.91.37.102
Elapsed Time: 8 ms.
Testing TCP port 80 on host autodiscover.tulisoft.co.in to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 216 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.tulisoft.co.in for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
HTTP Response Headers:
request-id: 35c38537-7f9d-4d32-82eb-dac2658583c7
X-SOAP-Enabled: True
X-WSSecurity-Enabled: True
X-WSSecurity-For: None
X-OAuth-Enabled: True
Cache-Control: private
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="autodiscover.tulisoft.co.in"
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: HOSTING
Date: Sun, 04 May 2014 13:39:05 GMT
Content-Length: 0
Elapsed Time: 422 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Elapsed Time: 676 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.tulisoft.co.in in DNS.
The Autodiscover SRV record was successfully retrieved from DNS.
Additional Details
The Service Location (SRV) record lookup returned host autodiscover.tulisoft.co.in.
Elapsed Time: 17 ms.
Attempting to test potential Autodiscover URL https://autodiscover.tulisoft.co.in/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 659 ms.
Test Steps
Attempting to resolve the host name autodiscover.tulisoft.co.in in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 138.91.37.102
Elapsed Time: 8 ms.
Testing TCP port 443 on host autodiscover.tulisoft.co.in to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 215 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 434 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.tulisoft.co.in on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=HOSTING, Issuer: CN=HOSTING.
Elapsed Time: 414 ms.
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name autodiscover.tulisoft.co.in doesn't match any name found on the server certificate CN=HOSTING.
Elapsed Time: 0 ms -
SPA 5xx and 9xx phones registering to all proxies with DNS SRV records
A weird situation -- I use DNS SRV records to prioritize the two Asterisk servers to register to (east coast vs west coast). However it seems that phones are often registering to BOTH servers and show as live on both at the same time. There seems to be little rhyme or reason as to when it occurs, but it's weird. Fortunately the phone does seem to be preferring the higher priority SRV record but I can't figure out why it is registering to both.
This happens with SPA-942s (6.1.5a) and SPA504Gs (7.4.9c).
Any ideas what makes this happen? On the surface it seems like a good thing, but functionally the phones are registering the same port numbers and only the priority server can get through firewalls with traffic for the phones. This screws up my "presence" indicators within the system.
DNS SRV RECORDS:
_sip._udp.west.server.net (for west coast customers)
Priority 10: west coast machine
Priority 20: east coast machine
_sip._udp.east.server.net (for east coast customers)
Priority 10: east coast machine
Priority 20: west coast machineWe determined this was not actually happening. There was a syncing taking place in the background that was giving the impression this was happening but it really was not.
-
Internal DNS - emailsrvr.mydomain won't resolve, IP does - www works.
Internal Mail won't resolve to emailserver domain, but LAN ip is fine
Hey gang, longtime reader first time poster.
After wrestling with this issue, i'm about out of ideas.
Here's my setup.
Leopard server 10.5.4, running OD master (all rocking),
AFP, Firewall, DNS, (mobile) network home directories.
I'll call this "xserve.mydomain.com "
Its NAT'd IP is 192.168.1.102.
It's a FQDN, kerberos is running and happy, all is well.
There are about 12
clients, each with a desktop (imac) and laptop (macbook).
I have a second (windows 2003 sbe) server hosting the following
services: Exchange and Web (for now).
I'll call this winsbe.mydomain.com
Its NAT'd IP is 192.168.1.101
My External DNS setup is this.
Our DNS hosting is done by our registrar (network solutions).
We own 4 static IPs from our ISP.
One IP is for our router/firewall providing NAT
to internal clients, and the xserve is on DMZ, with
its OSX firewall service turned on.
One IP is for the
windows server. (the last two, if you've been counting, are unused .
Via Network Solutions "advanced DNS", I have our zone
configured. "xserve.mydomain.com" points to its WAN
IP (66.xxx.xxx.198).
www points to 66.xxx.xxx.194.
MX records refer to "winsbe.mydomain.com" via
WAN IP 66.xxx.xxx.194 as well.
All outside services resolve correctly.
IE, i can hit the website and send/receive email from mydomain.com.
My internal DNS as setup as this:
primary zone= mydomain.com
nameserver= xserve.mydomain.com
mx record= winsbe.mydomain.com
xserve.mydomain.com has an A record to LAN IP.
winsbe.mydomain.com has an A record to LAN IP.
www is a CNAME record to winsbe.mydomain.com. <----i'm not sure about this one but it works.....
My forwarder IP points back to my Router (which seems to give me better performance than using ISP
DNS from here..)
I know this is working fine insofar as the webserver, as
an nslookup (www.mydomain.com) internally resolves www to 192.168.1.101.
mydomain.com and www.mydomain.com hit the webserver internally
on client browsers. rock.
Again, forward AND reverse nslookups internally resolve to winsbe.mydmain.com/92.168.1.101
Here is my guess as to my problem,
my internal hostname + a record for the windows server the same as the MX record
which has an alias from www.
I think it's getting effed in there somewhere?
If I setup email clients with the windows server LAN IP rather than
the domain "winsbe.mydomain.com" it all works fine.
I'd frankly be willing to half-*** it with this solution,
but each client will require a mobile computer, so we can't have that
I feel like i'm on the right track, but
just can't make the breakthrough.
Am I barking up the wrong tree here?
Here is a last question,
I have my firewall/router as the "Forwarder IP Address"
in the last page of Settings in server admin. When i put
my ISP's DNS servers, i always get a 2 second delay
for any web query on any client.
I have "127.0.0.1" as the first DNS entry in xserve Network Preferences.
The xserve is the only DNS entry in the client computers.
This isn't a "bad practice" or anything is it?For the curious, my named.conf below (haven't messed with it):
// Include keys file
include "/etc/rndc.key";
// Declares control channels to be used by the rndc utility.
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.
// Default controls
controls {
inet 127.0.0.1 port 54 allow {any; }
keys { "rndc-key"; };
options {
include "/etc/dns/options.conf.apple";
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
// query-source address * port 53;
// a caching only nameserver config
logging {
include "/etc/dns/loggingOptions.conf.apple";
// Public view read by Server Admin
include "/etc/dns/publicView.conf.apple";
// Server Admin declares all zones in a view. BIND therefore dictates
// that all other zone declarations must be contained in views. -
I am running a DNS server on a 10.6.6 box and want to add a 2nd IP to a DNS record on the LAN. The reason being is that I backup clients to a PresSTORE server onto tape. Some laptops are not always connected by ethernet so it would be handy to "drop back" to the wireless IP address. I have tried adding the 2nd (wireless) IP for a DNS entry but when pinging the client it only tries the 1st IP in the list. Reverse DNS points to both IPs. Is there a way of doing this?
Any help finding a solution would be greatly appreciated.
Cheers, PaulThis reeks of an IP subnet routing error, a DNS error, or of a firewall or connectivity issue.
No, No & No
DNS would not likely be my first stop here, if I do understand what you're up to. (And I'm not certain I do.)
OK this is as simple as I can think of asking... I have one DNS A Record for a client with 2 IP addresses, one IP for ethernet, other for wireless. Obviously they both can't have the same IP on the same subnet so if DNS lookup can't resolve to 1st IP, how can one force it to try resolving to 2nd before giving up with an error?
I guess the ethernet & wireless could have the same IP if they were both not active when both connected. But expecting the user to switch off wireless when the etherent cable is plugged in and switch back on when the cable is unplugged, for the same of simplicity of a network connection *+I think not+*.
Also with IPs in the A Record, I have found DNS always tries resolving to the higher of the 2 IPs first (192.168.1.35 before 192.168.1.36). Then if .36 is offline it won't try resolving to .35 again until the DNS cache has been flushed.
Are these using WiFi routers, or access points?
Simple Apple Extreme Base Station configured as a wireless access point.
Is there one IP subnet for all hosts irrespective of wired or wireless connection, or multiple subnets?
One IP subnet
Is there one DHCP server, or multiple DHCP servers?
One DHCP server
Is your PresSTORE box configured with static IP?
Static, not that is makes the slightest bit of difference.
By the look of it I am gonna have to wait until PresSTORE supports Bonjour! -
Installed Cisco Unity 7 on Windows Server 2000 and Unity Server is on Domain,and Exchange we are using is Exhcnage 2007. When we reach at Message Store Wizard it is showing some error at the end that " Failed reaching for Unity in Active Directory Global Catalog. The SVR Record may be missing in DNS Table" . It shows when we slected Exchange in Process and the Selected Storage Group. And the it takes time and then shows error. Please try to resolve this issue soon, we need this solution urgently. We have already spent several days on different issues regarding Unity.
If you need to talk regarding this matter, Please contact on +919780660619, and the conatct person name is Manav.
Thanks in Advance
RosyRosy,
We cannot call you from this forum. If you truly need a call, you can open a TAC case. The info I can tell you is that you need to fix this in your dns. A simple google search of "no SRV record Windows 2000 server" comes up with numerous resources that can help you fix this. Here is just one example.
http://support.microsoft.com/kb/241505
and
http://www.petri.co.il/active_directory_srv_records.htm
I would also advise you, if you are doing a new install with Unity 7 and that version of Exchange, that you use Windows 2003 as the OS. Even MS doesn't support Windows 2000 Server any more so if you end up having an OS issue on your Unity server, we will not be able to get MS to help you. From a support perspective, I would advise you to use Windows 2003 Server in this implimentation.
Thanks!
Tray -
Lync on premises with Exchange online UM SRV record
Hi,
We have Lync 2013 on premises and we have Hybrid exchange deployment, recently we have integrated Lync on premises with Exchange online UM, we have configured subscriber access and I have done all configuration, created hosted voice mail policy, created
Subscriber access UM contact.
Problem is that if a user dials from Lync client to voice mail (Exchange online UM Subscriber Access number) the call successfully establish, if the same user is outside the organization and wants to call the Exchange online UM Subscriber
Access number from his mobile or from his home phone number the call doesn't connect, this problem is not from the same user any one from outside the organization can not call to subscriber access number from his mobile or from his landline (outside the organization
numbers)
I have done some logging on Lync Edge server and found two things:
When a user calls from Lync client to O365 UM Subscriber access the call establish successfully and when I see the call logs I am seeing the
[email protected] and SRV record for the domain.com is verified
When a user calls from outside the organization (Landline or mobile) to O365 UM subscriber access the call doesn't establish and when I see the call logs I am seeing
[email protected] and subscriber access number as
[email protected] and the error says Unable to resolve DNS SRV record for domain it.domain.com.
Please note our internal domain is it.domain.com and our external or smtp domain is domain.com
In Lync 2013 the default sip domain is also it.domain.com and additional sip domain is domain.com
Pleasae help me to resolve the issue.
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft LyncThe issue is that your default domain is it.domain.com. I suspect that even if your Edge server is able to route this call back to Exchange online, that tenant will reject this call as it will not be able to find it.domain.com or federation SRV record associated
with it.
You will need to change your default SIP domain to your public SIP domain. If you decide to do this, please note that you will also need to review any impact on the simple URLs (and certificates if applicable).
It is also recommended to perform an export-csconfiguration command to backup the topology before making these changes.
Hope this helps.
SinghP80 -
Serious bug: call set-up problem in case of several DNS SRV records
Hello Cisco,
We have a MCU that consists of two servers in cluster. We have SIP SRV DNS records that point to both servers with equal priority and weight.
All applications work nice with such setup, except from Free Jabber. Jabber is unable to set up the connection most of the time. One time the connection is successful and 5, maybe even 10 times it is unsuccessful.
For testing, we removed SIP DNS records pointing to one server. This way Jabber works much better. There are some cases when the call set up fails but in most cases it works.
Looking the logs of the MCU, we can see three different ways, how call set-up may fail. It is probably unreasonable describe the details in this forum message. Anyway, it seems to be sure that in case there SIP SRV records point to one server then Jabber is able to connect the MCU, in case the records point to two servers equally then Jabber is pricnipally unable to connect the MCU. This bug should be fixed, IMHO.
Btw, what record does Jabber follow, is it _sips._tcp or _sip._tls?
Greetings and thank you in advance,
Marko LauritsHello Cisco,
We have a MCU that consists of two servers in cluster. We have SIP SRV DNS records that point to both servers with equal priority and weight.
All applications work nice with such setup, except from Free Jabber. Jabber is unable to set up the connection most of the time. One time the connection is successful and 5, maybe even 10 times it is unsuccessful.
For testing, we removed SIP DNS records pointing to one server. This way Jabber works much better. There are some cases when the call set up fails but in most cases it works.
Looking the logs of the MCU, we can see three different ways, how call set-up may fail. It is probably unreasonable describe the details in this forum message. Anyway, it seems to be sure that in case there SIP SRV records point to one server then Jabber is able to connect the MCU, in case the records point to two servers equally then Jabber is pricnipally unable to connect the MCU. This bug should be fixed, IMHO.
Btw, what record does Jabber follow, is it _sips._tcp or _sip._tls?
Greetings and thank you in advance,
Marko Laurits -
DNS (srv record missing for PDC)
Hi,
in our company we have a domain with 4 domain controller (all are Windows Server 2008 with domain functional level 2003).
In the DNS, under _msdcs.OURDOMAIN.priv -> _tcp there are only the SRV _ldap record related to 3 domain controller; there isn't the record related to domain controller that holds the PDC role.
From some months we have also issues about GPOs replicas between domain controller.
It makes sense to create the missing record ? There may be a valid reason because it is not present ?
Thank you.Hi,
Did the PDC host the DNS role at the same time? If yes, please make sure that you have enabled secure dynamic updates on the DNS server. You can stop and restart
DNS server by running the command below at the command prompt:
net stop dns
net start dns
On the PDC, please stop and then restart the Netlogon service by running the commands below to see if the SRV record is created in the DNS server:
Net stop netlogon
Net start netlogon
If the above solution is not helpful, please try to
manually enter the SRV records from Netlogon.dns file in \Windows\System32\Config or create on the DNS console.
Best regards,
Susie -
Hi
I have been doing an audit of our DNS zones and notice that some or other user has must have mistakenly registered their desktop as a kms host, since I see a DNS SRV record pointing to their pc on port 1688.
This has caused problems for us so much so that we now activate using another kms host that is not part of our domain. my question is this: can I go into dns and simply manually edit this incorrect SRV record to reflect the correct dns name of the working
kms host server?Hi,
Do you mean that you still cannot find out the host according to the record?
As a workaround, we can disable KMS host from publishing SRV record by creating a registry key via GPO. Even if someone configure a KMS host in your
environment, DNS record will not be published. Remember not to apply to your real KMS host.
Edit the GPO with the following:
Computer Configuration>Preferences>Windows Settings>Registry
Create a new
DWORD value called
DisableDnsPublishing in the registry, and set its value to
1. This value is at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform in the registry. To re-enable the default behavior for publishing of KMS SRV records to DNS,
set the value to 0.
Hope this helps. -
Adding SRV record in Advanced DNS control panel
Can I add SRV DNS record with more info than control panel allows? My clients has given me values for: Service, Protocol, Port, Weight, Priority, TTL, Name and Target.
I contacted 'live chat' and was directed to http://forums.adobe.com/docs/DOC-2511 which has the answer.
I've kept this question live in case anyone else has a similar problem. -
Is there a way to play video clips that use adobe flash and if not when are you going to resolve your problem with them ? I won't buy another apple product until you do and I Know I,m not the only one.
Use the search feature and type in Flash and there are like thousands of posts on this.
You seem to think you are addressing Apple with your post. This is a user forum and we are all users just like you. -
How do I add SRV record to my DNS for Office 365?
How do I add the following record?
Add the SIP SRV record for Lync web conferencing.
Create a new SRV record.
In the new record, make sure that the fields are set to precisely the following values:
Record Type: SRV
Service: _sip
Protocol: _tls
Port: 443
Weight: 1
Priority: 100
TTL: Set this value to 1 hour or to the equivalent in minutes (60), seconds (3600), etc.
Name: @
Target: sipdir.online.lync.com
Save the record.
Need help ASAP because my clients Email is down when I changed Domain Name Servers to Business Catalyst.
All Office 365 functions were lost.
Thank you for some assistance - URGENT,
Jim Vernon
Hopegate SoftwareHere is an image of the settings that Office 365 says i need to correct in my DNS settings on Business Catalyst:
Maybe you are looking for
-
Hi Gurus, We are facing a typical problem in BI Publisher when we are checking for a NULL value by using the following condition in the query. *((:P_EMP_NO IS NOT NULL AND EMP.EMPNO IN (:P_EMP_NO_I) ) OR(:P_EMP_NO_I IS NULL))* We have created report
-
each time i-tunes updates on my pc I lose the settings and have to import again - what is going wrong
-
Bulk deleting of payroll results in production
Dear all, I have run payroll for all employees into production as per client request, but now they want to delete all payroll results and again by maintaining few more details of employees they want to run payroll for all. Kindly tell me what tcode o
-
The iMac suddenly turns off while I'm working. I've owned the unit since August 2010 but this problem has just started occurring. I think it has happened three times in the past two week. I've heard about this problem, but have not experienced it unt
-
When I send or receive an email the date, to, from and subject line are fine but after that there is all of this encrypted information that is listed. I do not know what this information is called, how this information started showing up, I do not wa