DNS server's PTR record wrong?
I have a server I frequent that has an IP address of 10.1.1.2. It acts as an OD and AD server, DNS server, IM server and a few other things.
As of now, the DNS server only has 1 entry in it, for the DNS server itself. I got a request to add a second A record for a new accounting server. Easy enough right? I added an A record under my primary zone and made sure it was FQDN. I went to ping it by name and by IP and no luck - no resolution.
Whats odd is when I look at my records, I have 2 groupings of PTR records. One is my new one which makes sense : 1.1.10.in-addr.arpa. The other is the one that the DNS server originally had: 2.1.1.10.in-addr.arpa.
I'm thinking this is why I can't get my new A record to work.
I really REALLY don't want to kill OD or AD here. I know they lean on DNS to live. I have to get this fixed though. Can I delete both those records our of my primary zone, readd them, and all will work OK as long as I don't poke the primary zone? I'm assuming I can't rename a PTR record directly, right?
Any help would be super-duper appreciated! I have to fix this ASAP (obviously, right?).
Thanks!
Your DNS server isn't really serving out much in the way of DNS, it's running the self-hosted configuration that's the default when no DNS services were established during the Mac OS X Server installation and configuration.
And if DNS services aren't right, then yes, the rest of the stack tends to be spotty. Including OD.
Here is how to set up DNS on Mac OS X Server and then you should be able to migrate to correct DNS services without wrecking OD. This if your existing domain choice and set-up for the self-hosted DNS was correct.
Basically, you get to nuke the existing forward and reverse zone (the default install creates one of each), and establish a forward zone for your domain name (and not the host's FQDN), and add your host name (which doesn't need to be an FQDN in this context) into the forward zone. This will then apply the zone name to create the FQDN. Server Admin should then establish one or more reverse zones, and as needed.
Similar Messages
-
Child DNS Zone changing PTR record of OD Master
Grretings,
I am setting up a new OD master server for our school that will also host our DNS. Home folders will be on another server. I am using the DNS GUI for now. Setup master DNS zone of ourschool.lan. OD master has FQDN of admin.ourschool.lan with an IP address of 172.16.2.254. Forward and reverse lookups of OD master are great.
#host admin.ourschool.lan returns 172.16.2.254
#host 172.16.2.254 returns admin.ourschool.lan
When I go to set up a child zone, highschool.ourschool.lan, on this server I set the nameserver to ns1.highschool.ourschool.lan and IP address of 172.16.2.254, I have had the following happen:
#host admin.ourschool.lan returns 172.16.2.254
#host 172.16.2.254 returns ns1.highschool.ourschool.lan (not what I want!)
I understand forward and reverse lookups to OD master need to be rock solid. The changing of the PTR record is going to ruin this. Has anyone else seen this behavior. Should I just do the DNS through terminal and forget the GUI?
Thank you for any feedback. I searched this discussion list and didn't find anything similar to this in the postings.
Best Regards,
Steve
OS X Server and Client Mac OS X (10.4.6)Your problem stems from the fact you're trying to create two separate A records for the same IP address.
The GUI will automatically create a reverse DNS entry for each a record. Since you have two A records that point to 172.16.2.254 that's where your problem lies.
Your solution is either to use a CNAME (or alias) for the second hostname (e.g. ns1.highschool.ourschool.lan CNAME admin.ourschool.lan), or manage the DNS by hand and don't use the GUI tools. -
External DNS server not replicating records to secondary after migration from 2003 to 2012
Hi
I have a query relating to 2012 Server and DNS.
Last week we de-commissioned our primary external DNS server (Windows 2003 Server) and moved the role over to a new Windows 2012 server.
Since this point replication to our secondary server (3rd party hosted) does not seem to occur and our DNS records seem to have expired on the secondary server as we cannot look these up via nslookup.
I cannot see any failures in the event log of the server; I have checked our external firewall logs and nothing is being blocked inbound/ outbound as far as I can see. And the server’s local firewall has been disabled.
The server is a standalone server in a workgroup with a standard filebased primary zone, with no AD integration and recursion disabled.
When I created the zone I copied the .dns file from the old server and selected this in the interface during the creation of the zone on the new server. The new server has the same internal and external IP as the old server and the old server is off-line.
I have also manually increased the serial number of the zone and still no joy.
One thing that I have noticed is when I open the zones properties/Name Servers and click edit on the external nameserver I get the infamous "The server with this IP address is not authoritative for the required zone" error.
Any help Would be appreciated, thanks in advanceNice to hear that you are close in finding the problem. So in short:
You have enabled Zone transfers in DNS management console for the applicable zone
You have verified that your DNS is listening to the correct interfaces
You have enabled firewall rules to accept TCP and UDP traffic to port 53
You have checked if "BIND secondaries" option is applicable to your case
You have initiated a zone transfer from the secondary server
Lefteris Karafilis
MCSE, MCTS, SEC+
LinkedIn: http://www.linkedin.com/in/lkarafilis
Mail: [email protected]
Blog: http://www.karafilis.net -
Dear Community!
Could someone help me to fine-tuning DNS server configuration?
I'm configuring an IOS router act as a DNS server with the following parameters:
ip name-server [IP #1] [IP #2]
ip dns server
ip domain round-robin
ip domain name [domain.net]
The 1st DNS server is a public DNS server accessible from Internet, the 2nd one is a private corporate DNS server accessible from a site-2-site tunnel.
The client PCs at the remote end of the IPSec tunnel should query public DNS names from public DNS server, and the records of our private DNS domain.
Is it possible to configure a "policy" to query corporate DNS domain from a dedicated DNS server, and the other public DNS name from the public one?
Thanks in advance!
Best Regards,
Belabacsi
from Budapest, HungarySure, it's called DNS Proxy. It's not supported on all devices, so you'll have to check.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123relnt/800/rn830xc3.htm
DNS Proxy
In virtual private network (VPN), Point-to-Point Protocol over Ethernet (PPPOE), etc. PCs connected to the LAN may get Dynamic Host Configuration Protocol (DHCP) parameters including the IP addresses of the Domain Name System (DNS) server prior to the router connecting to the WAN to get the information over IP Control Protocol (IPCP). The objective with Proxy DNS (or caching-only name server) enables the router to receive DNS queries on behalf of the real DNS servers and proxy for the hosts on the LAN connected users. This enables the DHCP server to immediately send the hosts the router's own LAN address in lieu of the DNS server's IP address. The router forwards the DNS queries from local users to real DNS servers after the WAN connection comes up and caches the DNS records in response. Over the time, cache includes the DNS information most often requested by the local resolvers and this can reduce the overhead of packets to the WAN.
The router must obtain the correct DNS server information from the WAN in order for it to function as a proxy DNS server.
The global configuration command ip dns server enables DNS proxy server functionality on the router, and causes it to forward DNS queries to the actual DNS servers. The global configuration command dns-server address causes the router to respond to DNS queries with its own IP address.
HTH and please rate. -
PTR Record not Automatically Created in dns server
how to config when client joint to domian PTR Record Automatically Created in dns server
Hi Farzad_en,
Based on my knowledge , you need to allow Dynamic Updates .
"Open DNS Manager. To open DNS Manager, click Start, point to
Administrative Tools, and then click DNS.
In the console tree, right-click the applicable zone, and then click
Properties.
On the General tab, verify that the zone type is either
Primary or Active Directory-integrated.
In Dynamic Updates, click Nonsecure and secure."
For details please refer to following link:
http://technet.microsoft.com/en-us/library/cc794806(v=ws.10).aspx
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Leopard DNS Server: Zones with SPF records?
Hi all,
I'm trying to figure out how to setup SPF (Sender Policy Framework) records for some domains I'm currently managing with a Leopard DNS server and I don't see any documentation anywhere. Can someone please tell me if it's even an option? I'm new to running DNS with Leopard, so I could use all the help I can get.
Sincerely,
Israel
Message was edited by: Israel Thompson
Message was edited by: Israel ThompsonIsrael Thompson wrote:
So let me see if I have this right. Any changes I want to make that will not be editable in the GUI, I want to do them in db.mydomain.com instead of db.mydomain.com.zone.apple? Easy enough. However I tried adding "v=spf1 a mx ~all" (with quotes) to my file and it appeared to have broken the dns zone. What’s the proper way to enter these in manually? Can you give me an example of how it looks in your zone files? I’ve pasted a sample of mine below. Tell me if anything is wrong.
Israel,
I am new to Leopard Server - so I'm no DNS guru. I, too, have not used a DNS setup tool that requires a FQDN just associate an IP with the base of the domain (mydomain.com.). How did you get your 'mydomain.com. IN A 11.22.33.44' accomplished? Did you create a new A record and put mydomain.com. in the Machine Name field?
Here's my setup:
========================
db.mydomain.com
========================
;THE FOLLOWING INCLUDE WAS ADDED BY SERVER ADMIN. PLEASE DO NOT REMOVE.
$INCLUDE /var/named/zones/db.mydomain.com.zone.apple
========================
db.mydomain.com.zone.apple
========================
$TTL 10800
mydomain.com. IN SOA ns1.mydomain.com. admin.mydomain.com. (
2008010951 ;Serial
7200 ;Refresh
3600 ;Retry
604800 ;Expire
345600 ;Negative caching TTL
mydomain.com. IN NS ns1.mydomain.com.
mydomain.com. IN NS ns.mydomain.com.
mydomain.com. IN A 64.251.168.218
mydomain.com. IN TXT "v=spf1 ip:64.251.168.218 ip:64.251.168.220 ~all"
www IN A 64.251.168.218
mail.mydomain.com. IN A 64.251.168.220
mail.mydomain.com. IN TXT "v=spf1 a ~all"
xserve.mydomain.com. IN A 64.251.168.218
xserve.mydomain.com. IN TXT "v=spf1 a ~all"
ns IN A 64.251.168.218
ns1 IN A 64.251.168.220
mydomain.com. IN MX 10 mail.mydomain.com.
... where xserve.mydomain.com is my machine's hostname.
I have a funky setup for DNS because I don't have a different, or second, DNS server (just the one on my Xserve with everything else) and my name servers are under this zone. I added the two IPs for my mail and hostname to the base SPF record. Someone could still spoof from using the name or www domains (same IPs) but I can check for it using Postfix up front. I also added "v=spf1 a ~all" in case another mail server tries to check the mailing server or hostname directly.
You'll usually want to set a TXT "v=spf1 ~all" (SPF null) for any records that have no possibility for mail origins, like your ftp and mobile, but it appears you also have a similar issue to me - those services will be running under the same IPs as the mail service. This is why I added "v=spf1 a ~all" to all essential services (mail and hostname). I don't know what will happen if you add an SPF null to an unnecessary service that happens to also have the same IP. (Will the IP get blocked in a cache during a lookup??) So I didn't add an SPF TXT to those domains. I'm a little confused at this point. I should probably read more about it.
http://www.openspf.org/FAQ/Common_mistakes
Also, you'll notice I added FQDN to mail and xserve. If I do this and ensure they are in my reverse DNS PTR records then I've seen that when I add new zone records with same IPs (like for another domain) then the PTR records don't keep switching to the newest entry (why does it do that?).
I don't think your use of the . in the CNAME records is correct. I think the CNAME records are probably unnecessary since you have already fully defined the domains in A records. Also, those A records probably don't need FQDNs (with the ending .). I only added mine for the reason noted above, concerning the PTR records.
I hope someone who knows some more than I can chime in on this.
Larry
Message was edited by: Larry_S (removed mx from SPF TXT for main domain record, as it was redundant with the ip:) -
If there is no DHCP server on network then who will give PTR records to DNS server ?
For workstations, no. For some servers such as a mail server, perhaps but not critical. They're more important for public IPs, some email servers won't accept mail from your server if they can't properly perform a reverse lookup on the IP address.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications -
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 -
How many DNS record need to create in Internal & external DNS server for exchange?
Hi friends,
I recently installed Exchange Server 2010 in my organization for testing purpose and I've register a pubic ip too for exchange server on godaddy.com. How many
internal & External DNS records reqired to configure on external & Internal dns server so my all feature like Auto-discover, Activ -sync,& webmail start working perfectly.
It's my first time configuring exchange for a organization.
Thanks & Regards,
Pradeep ChauguleHi,
Just as what ManU Philip said, you need to create
Autodiscovery.domaincom and mail.domain.com for external dns server.
Generally, you configure your Exchange Servers as DNS clients of your internal DNS server.
Refer from:
http://technet.microsoft.com/en-us/library/aa996996(v=exchg.65).aspx
Best Regards. -
How to create A record on DNS server
How do i create an A record on the DNS server (windows server 2008) that would resolve into two ip addresses: PUB & SUB ip addresses respectivly, to enable EM redundancy in Cisco Unified Communications Manager 6.1.
Right now when the PUB failover to the SUB the EM does not work. the Phone services as well as the global directory does not work. the CUCM is fully integrated to LDAP.
Cisco recomends using an SLB but right now i am trying to use the DNS option. what i need now is how to create the A record on the DNS that would resolve into the two ip address of the PUB and SUB.You can do this but your results won't be quite as expected. I've played around with this and you'll see that the request for when you press the services button will go to server A, then when you click on the EM service your request will go to server B, then the login back to server A even though you started the login session with server B and back and forth, then with the authentication information, etc. Also DNS doesn't know about the state of your servers. If a server is down you'll still have issues if the name resolves to the down IP address. As far as I've seen DNS will always round robin with multiple records for the same name (unless you use an SRV record).
-
How to get Scavenged Records from Windows DNS Server uisng WMI API Call?
Hi Guys,
I'm facing one problem to find below things,
DNS Server have list of zones and each zones may have DNS Records. DNS Server provides an option set scavenging interval on server or in zone level.
Once records are old the server automatically apply scavenging process to remove that record.
I need to get DNS Records that are scavenged and timestamp using WMI Call?
sharavannaThe DNS log has this information. Just extract it from the log.
A scavenged record does not exisit when it is scavenged so it cannot be read from the DNS server. It has been deleted.
¯\_(ツ)_/¯ -
Serving static AAAA records with IOS' DNS server
Hi guys,
Has anyone managed to get IOS to serve statically defined AAAA records? I do this just fine with A records as such :
On the router :
ip dns server
ip host ns.example.com 1.1.1.1
ip host somehost.example.com 1.1.1.2
ip dns primary example.org soa ns.example.org [email protected] 21600 900 7776000 86400
From the Linux box :
unixhost$ dig @1.1.1.1 somehost.example.com
; <<>> DiG 9.8.1-P1 <<>> @1.1.1.1 somehost.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32168
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;somehost.example.com. IN A
;; ANSWER SECTION:
somehost.example.com. 10 IN A 1.1.1.2
;; Query time: 1 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Aug 15 00:42:11 2012
;; MSG SIZE rcvd: 50
Interestingly whenever I add a static ipv6 entry, I get the SOA as an answer instead of the actual AAAA record. But from the router itself, it can use the statically defined hosts just fine.
On the router :
ipv6 host somehost.example.com 2001:1:1:1::2
From the Linux box :
unixhost$ dig -t AAAA @1.1.1.1 somehost.example.com
; <<>> DiG 9.8.1-P1 <<>> -t AAAA @1.1.1.1 somehost.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53347
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;somehost.example.com. IN AAAA
;; AUTHORITY SECTION:
somehost.example.com. 86400 IN SOA ns.example.com. [email protected]. 3553994542 21600 900 7776000 86400
;; Query time: 1 msec
;; SERVER: 192.168.200.252#53(192.168.200.252)
;; WHEN: Wed Aug 15 00:42:22 2012
;; MSG SIZE rcvd: 108
But from the router, it works just fine :
router#ping ipv6 somehost.example.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:1:1:1::2, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/4 ms
I'm running 15.2(2)T1.
Thanks,
Eric LauriaultHello Everyone,
in case someone runs into this thread: In our case it turned out that the problem was related to the DNS Server service. Regardless of the above configuration settings on the NIC and in the registry, the DNS server will always register in DNS using
all of its IPs that the service is listening on. To change this behaviour you can tell the DNS service to only register individual IPS in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\DNS\Parameters
Add a Reg_Multi_SZ called "PublishAddresses" and specify the list of IPs
In our case we added just one of the three configured IPs and from then on the server only registered this address and not the other ones.
Regards
HarryNew -
We have a Server 2012 R2 DNS Server in our network.
The problem is I did a DNS test at intodns.com and it returned an error:
ERROR: No reverse DNS (PTR) entries.
While I've configured PTR for the domain name in DNS server.
ping -a command return domain address if I'm connected to internal network.
This is a serious problem since our users can't send e-mail from our mail server.ZoneType=primary
isautocreated= false
isdsintegrated= false
isreverselookupzone= false
issigned= false
For reverse zone
ZoneType=primary
isautocreated= false
isdsintegrated= false
isreverselookupzone= true
issigned= false
Sorry for changing format. -
Server 2008 DHCP is handing out the wrong DNS server.
We have two new 2008 DC that handles, DNS, DHCP and WINS. Our DHCP scopes have been migrated to these servers. We are seeing some random issues where clients are using the new dhcp server but the old dns server information is listed for the some systems. We discover this by using network monitor on the old DC, DNS, DHCP server. Once the client performs a ipconfig /renew, the problem is corrected. Any ideas?
Hi BrianAuH20,
Thank you for posting here.
Based on your description, I understand that your Windows 2008 DHCP server hands out the wrong DNS server address.
To troubleshoot this issue, please perform the follow steps to see whether the clients retrieve the right DNS server address.
1. Temporarily make the old DC, DNS, DHCP server offline.
2. Check the new 2008 DHCP server setting.
i. In the DHCP console tree, under Scope [172.16.0.0] SS Scope, right-click Scope Options, and then click Configure Options.
ii. On the Advanced tab, verify that Default User Class is selected next to User class.
iii. Select the 006 DNS Servers check box, in IP Address, under Data entry, type DNS Server IP address, and then click Add.
iv. Select the 015 DNS Domain Name check box, in String value, under Data entry, type your domain's FQDN name, and then click OK.
3. Restart the DHCP service.
For more information, you may refer to:
http://technet.microsoft.com/en-us/library/ee404786(WS.10).aspx
Hope this helps.
Sincerely,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights. -
DNS Host record of a computer is deleted after you change the DNS server assignment
Hi All,
This is a critical bug in Windows 7/Windows 2008 and Windows 2008 R2. Is there any way to get rid of it? I am planning for for a deployment with new DNS server IPs.
Thank you.Hello,
please see http://support.microsoft.com/kb/2520155/en-us
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Maybe you are looking for
-
Backing Up Music on External Hard Drive
I want to back up all of my music on an external hard drive. I highlighted all of my songs, which is over 2,000 and dragged them to my external drive, like i would with anything else. But the songs wont transfer to the external drive. Is there anothe
-
Hello: every time I have been on the internet lately, I have been getting bombarded with pop-ups from a couple of sites, but most of them come from ConvertFilesForFree, prompting me to connect to their site for some such reason. I'm not certain wheth
-
Parallels destop or Boot Camp?
I'm in the market for a new MacBook and would really like access to all those Windows games out there. But I am unsure if Parallels Desktop or Boot Camp would be best the best program to get the best quality out of the games. I don't need it blazing
-
Can I use firefox in webview? what is the package name and the activity name?
Can I use firefox in webview? what is the package name and the activity name? I saw : intent.setClassName("com.tencent.mtt", "com.tencent.mtt.MainActivity"); but what is the name for firefox?
-
I have 45:59 mins lecture and one picture, can't export to QT with one file
I have a lecture of a duration of 45:59 mins. and one slide (picture). I have created a slide show in Keynote (v. 5) and wanted to export to QT for YouTube uploading. I end up having two files! and when I upload to YouTube, it fails for not being the