DNS Name is not resolved.
We have VPN 3005 Concentrator (4.7.1) and VPN client 5.0.3. We setup Split tunneling.
When some user opens the application, sometimes the DNS name is resolved, sometimes it is not.
When the DNS name is NOT resolved, we manually put in the IP address of the server. Then, the application is open.
How do we make DNS resolve consistently?
Thanks.
You check to check the split-dns settings. Also can this local DNS server (split tunnelled) resolve those names even without the VPN?
Regards
Farrukh
Similar Messages
-
DNS Server does not resolve new generic Top Level Domain names- CNR configuration issue?
Hi all,
I am not sure if this is the correct community to post this question, but I will give it a try. I noticed that the users of my network cannot resolve web sites using new top level domain names, like ".education", ".international", etc. I have an internal DNS server made by Infoblox and a Cisco CNR v6.3.3.1 as an external DNS server. Infoblox uses CNR as its forwarder and CNR uses the root DNS servers for queries.
I would think that CNR was the problem because it is an obsolete product but after speaking with a fellow engineer at another organization where they still use an older version of CNR than mine, they have no problems at all. So now I am thinking it is a setting either on Infoblox, or on CNR I need to change. I can see Infoblox is forwarding the requests to CNR but that's about it. I am not sure if CNR is discarding the request. When I do an nslookup from a PC in my network it does not matter if I set my DNS server to be the Infoblox or the CNR. Neither resolves the URL.
Then again, no matter what I lookup using the CNR as my DNS, I only get a response with the root DNS names and IPs!
Any help is appreciated!Hi Constantinos,
Have you taken a look at the infoblox community site? We've just reposted your question there and alerted some internal SMEs that should provide a solution soon.
https://community.infoblox.com/forum/ddi/dns-server-does-not-resolve-new-generic-top-level-domain-names-cnr-configuration-issue
Best,
Eric -
We would like to request Microsoft Remote Desktop (MRD) to behave the same as the open source CoRD.app on OS X with respect URL resolution.
Example:MRD will resolve from Terminal rdp://full%20address=s:<IP or DNS Name>, but not rdp://<IP or DNS Name>
As the OS will respect any of the following protocols in Terminal or browser:
afp://<username>@<IP or DNS Name>
cifs://<username>@<IP or DNS Name>
ftp://<username>@<IP or DNS Name>
ftps://<username>@<IP or DNS Name>
http://<username>@<IP or DNS Name>
https://<username>@<IP or DNS Name>
smb://<username>@<IP or DNS Name>
ssh://<username>@<IP or DNS Name>
vnc://<username>@<IP or DNS Name>
(<username> can be omitted to force authentication at connection) it seems slightly redundant to force "full%20address=s:" in the URL.
Can Version 8.0.1.6 be modified address this request?
What is the proper way to report an enhancement request or bug?
Thank you for your consideration.Hi,
From your description it appears that you want to modify the pattern for assigning the rdp full address but this doesn’t support as per your requirement. That is the default string which we need to have for passing full address.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
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 -
DNS workng but not resolving itself
Just promoted my 1st 2012 server to DC to replace 2003 DC. DNS has replicated to 2012 and zone entries are the same on both servers. The hostname of the 2012 server is not resolving even though there is entries in DNS on both servers for it.
DNS on the 2012 server seems to be resolving everything else correctly except it's own name. Network discovery and file share are enabled. The NIC on both servers has the IP address of the 2003 server for DNS. I can get to the 2012
server if I use it's IP address but Client computers need to be able to get to the 2012 server by hostname.try :
1. Restart DNS services
2. run these commands on server :
ipconfig \flushdns
ipconfig \registerdns
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread. -
DNS names don't resolve properly
I have an AirPort Extreme I am using for my home router. No problems with it until I setup an unRaid NAS server for media. Now I always have problems with web based control of the unRaid because names won't resolve properly on my local network. Only IP addresses. I was able to work around this problem by editing the hosts files on the desktop computers on my network, but that's not possible with iPhones as far as I can tell. It looks like the real problem is the DNS server on the AirPort Extreme. Does anyone have any idea how I can correct this issue? I haven't been able to find any settings for the DNS server other than the WAN IP. Should I go ahead and spend a few bucks for Mavericks Server? I have a couple of machines I could run it on, just not sure how complicated it is to setup. I'm not an IT professional.
And if I used one of my computers (MacPro probably) running Mavericks Server as a router would that work?
I have not tried it.. usually a server will be able to handle a lot more complicated setup than a domestic router can.. the only issue is how much of the networking do you want the server to take over.
Or if I configure the unraid to use the name brunnhilde.local?
That should be added by default.
Do a netstat scan from a computer on the network. That will show what shows up and what doesn't. By default Apple routers should be adding local to anything they supply a dhcp address to.
You should not use fixed static IP in the unraid .. you should always use dhcp reservation in the router. Otherwise it is simply not going to appear or appear correctly in the arp table of the router.
I'm not sure what other options are supported by airport other than IP?
Sadly what you see is what there is.. there is no advanced access to the router cli or any such thing. Albeit I am working on it. I doubt you will like my solution. (soldering in a serial port). And a lot of the system commands are difficult to find and use. So this is not like a regular router at all.
Rather than use Mavericks Server.. why not invest in a better router.. you can keep using the AE for wireless and switch purposes. -
SCAN name could not resolve in Oracle 11g R2
Hi all,
I have a setup of 2 node with Solaris 10u8 machine for Oracle 11g R2 RAC.
I entered the scanip in windows DNS.
When i try to nslookup from solaris it is not getting resolved.But from the DNS it is getting resolved.
I have changed as nsswitch.conf file and created resolve.conf and entered the proper entries.
Please help me..
Regards
BobsHi all
I resolved it.
Issue was my resolv.conf was named as resolve.conf.
I changed the file name as resolv.conf and the problem got solved.
Now i can resolve the scan ip through nslookup scan-name
Regards
Bobs -
DNS Name is not updating of domain controllers
Hi
DNS Host name is not showing FQDN.. See below figure..
How can i change it to FQDN..The figure is very small to be seen but it seems to be coming from computer properties in ADUC.
In this case, the attribute that is managing this valued is named dDNHostName. You can refer to this KB which might help: http://support.microsoft.com/kb/240942/en-us
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password -
Gethostbyaddr() and reverse DNS name do not match
So we updated to 10.4.6 on our server... and now none of the clients can connect...
Our DNS and reverse DNS (done by the university IT group) have caps in them... but all the home directories for users are lower case...
How can I fix this - short of entering all home directory info in by hand? Oh - suggesting that the IT group change the DNS is not helpful as it will not happen.
Mac OS X (10.4.6) ServerA summary - Here's the situation:
1. I have a 10.4 server running on a G5 tower.
2. The DNS is operated by the university IT group and our reverse DNS is mixed case... asked and they're not going to change it.
3. 10.4.6 introduced some funky stuff with FQDN, DNS and case sensitivity issues.
So... before I changed anything after the 10.4.6 update... users couldn't log in because it couldn't get their home directories...
The automounter would be looking for:
/Network/Servers/servername.Psychology.McMaster.CA/Users/username
While if you looked in /Network/Servers/ you will see:
/Network/Servers/servername.psychology.mcmaster.ca
(note the case)
Alright - moving on:
4. Tried changing hostconfig HOSTNAME - only worked on local server (and you're not supposed to do this anymore).
5. Used changeip same IP address, lower-case name to mixed case name... now users could log in.... glory!
6. Argh... they can log in, but can only intermittently actually get their home directories... seriously. You log in, see your desktop and flash it's gone... clicking on your home directory or desktop in finder gets you 'The volume for "Desktop" cannot be found'... doing "cd ~" and then "ls" from a terminal window sometimes gets you your directory, a partial directory or an error... and even then the ownership maybe the user or root...
7. Looking in the logs we see:
May 25 14:48:26 client kernel[0]: AFP_VFS afpfs_unmount: /private/Network/Servers/servername.psychology.mcmaster.ca/Users, flags 524288, pid 490
May 25 14:48:26 client kernel[0]: AFP_VFS afpfs_MountAFPVolume: GetVolParms failed 0x16
May 25 14:48:26 client automount[490]: Can't mount servername.Psychology.McMaster.CA:/Users on /private/Network/Servers/servername.Psychology.McMaster.CA/Users: Invalid argument (22)
May 25 14:48:26 client automount[490]: Attempt to mount /automount/Servers/servername.Psychology.McMaster.CA/Users returned 22 (Invalid argument)
May 25 14:48:26 client automount[489]: Can't mount servername.Psychology.McMaster.CA:/Users on /private/Network/Servers/servername.Psychology.McMaster.CA/Users: Invalid argument (22)
(server and client names changed to protect the guilty).
I'm stumped... and it's to the point that the owner of said server (a staunch apple supporter) is asking if I can replace the server with a Linux box with LDAP/AFP/SMB...
Any help here? -
CSCtw45592 - CLI "NTP Server dns name " - does not get synced to standby
15.1(3)T4
Hi David,
This bug is not shown as resolved in 15.1(3)T4;
http://www.cisco.com/en/US/docs/ios/15_1/release/notes/151-3TCAVS.html#wp54837
Known Affected Versions: (65)
15.2(1)S,15.1(3)T3,15.1(3)T2,15.1(3)T1,15.1(3)T
15.1(2)T4,15.1(2)T3,15.1(2)T2a,15.1(2)T2,15.1(2)1
15.1(2)T0a,15.1(2)T,15.1(2)GC1,15.1(2)GC
15.1(1)XB3,15.1(1)XB2,15.1(1)XB1,15.1(1)XB
15.1(1)T4,15.1(1)T3,15.1(1)T2,15.1(1)T1,15.1(1)T
15.0(1)XA5,15.0(1)XA4,15.0(1)XA3,15.0(1)XA2
15.0(1)XA1,15.0(1)SY,12.2(50)SY1,12.2(50)SY
12.2(33)SXJ2,12.2(33)SXJ1,12.2(33)SXJ
12.2(33)SXI8a,12.2(33)SXI8,12.2(33)SXI7
12.2(33)SXI6,12.2(33)SXI5a,12.2(33)SXI5
12.2(33)SXI4a,12.2(33)SXI4,12.2(33)SXI3z
12.2(33)SXI3a,12.2(33)SXI3,12.2(33)SXI2a
12.2(33)SXI2,12.2(33)SXI1,12.2(33)SXI
12.2(33)SXH8b,12.2(33)SXH8a,12.2(33)SXH8
12.2(33)SXH7w,12.2(33)SXH7v,12.2(33)SXH7
12.2(33)SXH6,12.2(33)SXH5,12.2(33)SXH4
12.2(33)SXH3a,12.2(33)SXH3,12.2(33)SXH2a
12.2(33)SXH2,12.2(33)SXH1,12.2(33)SXH0a
12.2(33)SXH
Less
Fixed in: (17)
15.2(3.30)PIP,15.2(2.9.6)PIH18,15.2(2.14)PI19d
15.2(2.14)PI19,15.2(2.10)S,15.2(2)T0.12,15.2(2)S
15.2(2)GC,15.2(1.18)S0.8,15.2(1)T2.12,15.2(1)S2
15.2(1)S1.3,15.1(4)XB8,15.1(4)M3.8,15.1(2)SIV11.10
15.1(1.23)SID,12.2(33)SXJ3.36
Cheers!
Rob
"Always movin' ahead and never lookin' back" - Springsteen -
Airport Extreme 802.11ac local dns not resolving
I have an AirPort Extreme 802.11ac wireless router that I cannot get to resolve local dns names and entries. Everything else is working perfectly, even external dns resolution, but any local dns hostname does not resolve. I can ping the ip addresses of all local systems, I just cannot resolve them. I have checked all configurations and they are set correctly. Please help
adbrennick wrote:
Update:
Setting the AE in Bridge Mode works fine.
Because the dns is then moved to the main router.
Apple are bent on removing as much as possible from even what little was available in 5.6 utility.. so each update removes yet more options.. as for having telnet or ssh .. go wash out your mouth.. they are anathema to Apple total control of the environment.. I mean to say you might set something they didn't intend. -
Still cannot resolve "gethostbyaddr() and reverse DNS name" warnings.
"Mar 15 11:02:48 xs1 servermgrd: servermgr_dns: gethostbyaddr() and reverse DNS name do not match (xs1.dept.school.edu != xs1.dept.School.EDU), various services may not function properly - use changeip to repair and/or correct DNS"
I have two xserves, both of which keep generating the same warnings, ad nauseam, in /var/log/system.log and having followed all suggestions and instructions in discussions, technical notes, afp548.com, and from other sysadmin's I still cannot stop them. There do not seem to be any services affected, or at least not in an overt manner.
Both xserves run slightly different services: (xs1) AFP, Firewall, NetBoot, NFS, Open Directory (slave), Print and Web; and (xs2) AFP, Firewall, Open Directory (master) and Software Update.
On both xserves I have run the following commands/tests with correct results, yet still I get the warnings in system.log: "changeip -checkhostname" is correct, and "scutil --get HostName" is correct. The /etc/hostconfig file is correct with "HOSTNAME=-AUTOMATIC-".
The only thing I can consider is that when setting them up, I had entered the FQDN in all lower-case, but the reverse dns is not, our domain is capitalized, and the tld is in all caps on the DNS servers. I had ages ago issued the "changeip" command as recommended in the warning, to no effect, even though "changeip -checkhostname" says it's correct.
Where the heck to I look now? This is driving me nuts!
RackMac1,1 & RackMac3,1 Mac OS X (10.4.8)>As of 10.4.6, Apple states to never change /etc/hostconfig's HOSTNAME entry.
Inside the little black box that Apple runs Mac OS X Server this might be good advice. However, in the real world, real servers are often outside of Apple's box (sometimes far outside) and you have to do certain things that Apple don't advise or 'support'.
I can't tell you how many things I run on my servers that are outside the box and judging by other posts on these boards I'm not the only one. You only have to look at DNS, web and mail for starters to see that Apple's model doesn't cover everyone's needs. -
Problem with DNS - ping/Safari cannot resolve, but host/dig work OK
Hi All,
Have a weird problem with DNS which is a bit similar to the following ones:
http://discussions.info.apple.com/thread.jspa?threadID=2190208
http://forums.macrumors.com/showthread.php?t=337942
I connect with remote internal network via OpenVPN and from time to time (yes, intermittent problem :)) internal DNS names cannot be resolved.
When it happens I can still resolve names using host or dig utilities, but applications (like Safari) and ping cannot resolve them.
resolv.conf has proper DNS server set:
*$ cat /etc/resolv.conf*
*# Mac OS X Notice*
*# This file is not used by the host name and address resolution*
*# or the DNS query routing mechanisms used by most processes on*
*# this Mac OS X system.*
*# This file is automatically generated.*
*domain openvpn*
*search openvpn*
*nameserver 10.0.0.1*
More than that - it can resolve those internal names when queried directly, for example using host:
*$ host YYY.XXX.ru 10.0.0.1*
*Using domain server:*
*Name: 10.0.0.1*
*Address: 10.0.0.1#53*
Aliases:
*YYY.XXX.ru has address 192.168.x.y*
but at the same time ping reports "*Unknown host*":
*$ ping YYY.XXX.ru*
*ping: cannot resolve YYY.XXX.ru: Unknown host*
I tried "*dscacheutil -flushcache*" and it did not help. Also tried to comment out domain and search directives in resolv.conf and it did not help as well (and actually it should not matter).
Any ideas why this can happen and what else can I check when it happens again?
Thanks!I have the same issue. It cropped up after I installed updates to MS Office 2008 and Firefox in which I also saw issues with the icons disappearing in the dock of the applications that were open when I started the Office update. I rebooted to try to get them back, but ended up deleting them and restoring from the Applications folder. I don't know if that's a red herring or not, but I generally try to figure out what has recently changed that may cause something to suddenly start failing.
I'd been working successfully all morning before it started acting up. Switching from wifi to cat5 had no effect.
@realaaa, were you able to resolve without a major undertaking, like reinstalling your OS?
pnmbp:~ pn$ dig goo.gl
; <<>> DiG 9.6.0-APPLE-P2 <<>> goo.gl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40996
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;goo.gl. IN A
;; ANSWER SECTION:
goo.gl. 140 IN A 74.125.45.139
goo.gl. 140 IN A 74.125.45.102
goo.gl. 140 IN A 74.125.45.113
goo.gl. 140 IN A 74.125.45.138
goo.gl. 140 IN A 74.125.45.101
goo.gl. 140 IN A 74.125.45.100
;; Query time: 27 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Mon Dec 13 16:59:34 2010
;; MSG SIZE rcvd: 120
pnmbp:~ pn$ ping goo.gl
ping: cannot resolve goo.gl: Unknown host
pnmbp:~ pn$ curl <a class="jive-link-external-small" href="http://">http://goo.gl
curl: (6) Couldn't resolve host 'goo.gl'
pnmbp:~ pn$ host goo.gl
goo.gl has address 74.125.45.100
goo.gl has address 74.125.45.101
goo.gl has address 74.125.45.138
goo.gl has address 74.125.45.113
goo.gl has address 74.125.45.102
goo.gl has address 74.125.45.139
pnmbp:~ pn$ -
Hi,
connecting to the JMS-Provider by a JAVA-Client, the P4-Provider returns the IP-Address of the host.
Being in an environment with different domains, we have to work with the DNS-name of the JMS-Provider and not with the IP-Address.
Is it possible to configure, that the P4-Provider returns the DNS-Name and not the IP-Address of the host.
Regards
DirkHi,
You can configure JMS on the 'Visual Administrator' under Instance-> Server-> Servcies-> JMS Provider.
Refer Configuration of External JMS Provider at
http://help.sap.com/saphelp_nw04/helpdata/en/cd/4d4941abbb4c0de10000000a1550b0/frameset.htm
also the blog below providing details on 'JMS Setup'
/people/glenn.kealey/blog/2004/06/07/porting-a-j2ee-application-to-sap-webas-and-open-sql-part-i
Regards,
S.Divakar -
Where does ARD get it's DNS information from? Wrong DNS name reported.
It's very strange...ARD is reporting a DNS name for one of my servers that has long been removed from my network. I can't figure out where it's pulling this info from? The servers real DNS name is not being reported at all. I know the IP this new server has is a recycled IP from an earlier server that may have had that DNS name associated with it but that was literally three years ago. How do I change this? Whenever I try to rename it manually it just flips right back.
Hi Rab1967 ,
The first question :
The IP addresses are from host records .The name of the record is the domain name(In the zone ,the name is displayed as “ same as parent folder “ .) .
The second question :
When we type characters in nslookup ,it will query for host records by default .To see the settings of nslookup ,type
set all .
For detailed process of the query ,we can use debug mode of nslookup .
To enter debug mode ,type
nslookup and then type set d2 .
Here is the guide for using nslookup :
Nslookup :
https://technet.microsoft.com/en-us/library/cc940085.aspx
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Maybe you are looking for
-
Ipod touch is showing in my computer but not itunes?
Please help me, i have tunred my laptop and Ipod on and off i have reinstalled a newer version of itunes, i have also tried using different USB ports. It shows my ipod in my computer but not in itunes!
-
"Internal error occurred" when launching Acrobat Pro X (AAMEE 3.1.150.0)
AAMEE 3.1.105.0 generated packages run fine when pushed to Macs that do not have an existing previous version of CS. However, if pushed to a Mac that has CS4 installed, CS6 installs but Acrobat Pro X will not launch ("Internal error occurred"). We ar
-
Can I set a default to effect settings? Or apply the same effect settings to multiple clips?
If I want to set multiple clips to have the same effect, can I do that without resetting the effects every time I add it? Or can I set a default setting to an effect that is different from the default default?
-
Please, please, please help me! I have so many songs on my iTunes. I would really appreciate any help!
-
Disappointed about the support
i am very disappointed about the photoshop support, i bought software for more than 1000€ and thats the official support? No german support, no phone support, no mail support, thats not serious! Chatsupport: the chat dont offer support for questions