Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium







The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Share tech news, updates, or what's on your mind.

Sign up to Post

We currently have a fairly simple set up, we have ONE public Web Server IP.   Our In/Out path is ISP line to our Cisco ASA/Firewall to our Host Server.    We use Static IPs from the ISP.   Our objective is to achieve highly reliable access to our Web server.  

We are looking at solution such as DNSMadeEasy + DNS Failover.  

Would the following plan work?
1) We'll acquire a new ISP #2 service as backup for our ISP #1 service.
2) We'll acquire a new Switch. On site our location we'll plug the two lines from ISP #1 and ISP #2 into the new Switch.
3) Run a single line from this new switch into our existing CISCO ASA router, and add configuration rules to Cisco for the new source IP addresses to mirror the rules already there for NAT, port forwarding, etc.

Any recommendations would be appreciated!
Veeam Disaster Recovery in Microsoft Azure
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

I have 2 DC's running win 2008 32bit also Running DNS, DHCP with Domain Functional Level of Windows Server 2008.
I want to introduce a Windows Server 2012 as a DC and transfer the FSMO but I still want to keep running DNS and DHCP on th eolde 2008 32bit servers. ANY recommendation as of what steps should I take and should I also move DNS and DHCP to the new server?
Hi support

We have major issue that after being remove from the MPLS that some of the traffic unable to reach google or microsoft  DNS .

How to resolve fix a ip address to test out the DNS ?
Hi All,

I recently had to rebuild a Windows Server 2k12R2 Server. Current Set-Up

2 x Windows Server 2k12R2

DC01 has all the FSMO roles
DC02 (before rebuilt) - kicked it off the domain, demoted the server
DC02 (rebuilt) - I gave it the same name and IP address as the one that I demoted.

  • I'm unable to replicate, when I do repadmin /syncall, it says that the RPC server is unavailable
  • I am able to ping the rebuilt DC02 by IP
  • I have attached a screen shot of dcdiag
  • It says no host record, but when I check the DNS manager of DC01 and DC02, I do see it
We have a Windows 2011 SBS server.   We never used the Exchange built in but it appears that our Outlook 2013 on the Windows 7 desktops have an ost file setup and the old external pop3 email we used with a small ISP for email.
We are switching to Office 365 shared Exchange and getting rid of the pop3 email.  We have setup the users in Office 365 admin portal.  Have exported the Outlook pst files on the individual users Outlook 2013 desktops.  We uninstalled Office 2013 from the desktop.  Downloaded and installed Office 2016 from the Microsoft Office 365 portal.       when starting Outlook 2016 on the desktop it tries to connect to the ost file we never used on SBS server and also the old pop3 email.   Do we need to delete the user's Outlook Profile and create a new one?  How do we do that and will it cause a problem with the users internal network login?  Will Windows SBS server try to force internal use of the Exchange built into it?
Do we need to actual remove the user from active directory in the Windows SBS console or can we just delete the Outlook profile   As I understand it things need to be done in  the SBS console or it may affect the whole server and network
We recently took over a domain controller and an Exchange Server, both Windows 2008 R2, with e-mail connectivity problems. We soon found invalid AAAA records in DNS. They were pointing to the IPv6 addresses of the hosts' 6TO4 tunnel adapters, not to the addresses of their physical LAN adapters.
We then deleted the wrong AAAA records on the domain controller's DNS server only to see them re-appear again within a couple of hours, breaking Exchange communication again. Who/what keeps registering these records? How do we keep them off?
("Register in DNS" in LAN connection properties is unchecked; all servers are IPv6-autoconfiguring.)
I will be installing a Windows Server 2016 Essentials server to replace an existing SBS2011 server.  They will use Exchange Plan I and II and Outlook 2010/2013/2016 clients.  When I install W2K16 Essentials I will need to configure DNS entries to so Outlook can successfully authenticate, etc.  Exchange autodiscovery needs to be setup correctly so that each Outlook client successfully authenticates and maintains a connection to their hosted mailbox.  I am looking for the steps necessary to setup the local DNS entries.  Your feedback is appreciated.
I was updated one of my domain controllers that is the FMSO role holder.

The updates failed and the machine was rebooted.

Now the machine seems slow, sluggish and other severs and services wont authenticate against it properly.

My other domain controllers now wont even recognise that they are domain controllers.

They are up, DNS is running, but the network shows as "network 2" on public.

I have tried changing the network adapters uninstalling etc, but whenever i try to run anything to do with the domain such as ADUC it comes up saying no domain controllers can be found.

Need some help asap please. nothing i try seems to work.
Looking for a script that will go out and check if DNS is SET to DHCP. The script will run against all the computers in the network.  The output should only contain the name of Computers that are not using DHCP Option for DNS.

Thanks in advance
Hi All Experts.

I've network with new Exchange 2013
Computers (Windows 10) with Outlook 2007 and 2010 (domain members or not) doesn't have any problem to connect to Exchange
Outlook 2013 and 2016 computers that are not part of domain (Windows 10 home edition) has problem to configure outlook.
For the first time when I try to connect new profile to Exchange Outlook is asking for Name, email and password, then is keep prompting for password all the time.

There is no way to connect.

I assume there is some problem with new way of authentication in new Outlook 2013 and 2016 but I can't figure out what I need to change in my network configuration to make this work.
[Webinar On Demand] Database Backup and Recovery
LVL 11
[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Hello, I am trying to migrate a DC from Windows SBS 2008 server to a Win 2012R2 Standard server.  I have downloaded dcdiag and I have problems now with the domain controller being found.  I have not yet demoted the 2008 SBS Server.

I have reviewed the DNS and cannot get the connectivty test to work correctly which I beleive is part of the problem.

the dcdiag results are as follows:

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   Testing server: Default-First-Site-Name\xyz2017
      Starting test: Connectivity
         The host bd8c4734-d1d3-4a57-8422-d17200041a41._msdcs.abcinc.local could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name

         (bd8c4734-d1d3-4a57-8422-d17200041a41._msdcs.abcinc.local) couldn't

         be resolved, the server name (xyz2017.abcinc.local) resolved to the

         IP address ( and was pingable.  Check that the IP address

         is registered correctly with the DNS server.
         ......................... xyz2017 failed test Connectivity

Doing primary tests
   Testing server: Default-First-Site-Name\xyz2017
      Skipping all tests, because server xyz2017 is
      not responding to directory service requests
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
The client is no longer using Exchange on SBS, so I just need to move AD accounts and DNS responsibility to the new Windows 2016 server. This is a little above my level of expertise. Thanks for your help!
Long story short.  Our marketing person reached out to our web hosting company to make some changes to some records (CNAME, etc.) to verify our domain with MailChimp to ensure that our marketing emails were not getting flagged as spam.  I am not sure what our web hosting company did but they did not make the correct changes and things broke instantly.  Our website went down, outside sales cannot utilize their VPN connection, email stopped coming in, etc.  

I began trouble shooting the problem yesterday.  It appears that the web host changed the nameservers.  I updated the new nameservers with our domain registrar and our website came back online.  

The webhost also changed our MX Record to point to their webserver instead of our public IP address for our internal Exchange server.  I changed the MX Record back to our public IP address and email is flowing properly again.

However, the use of Outlook outside of our internal corporate network is not working.  Upon opening Outlook, a message pops up stating:

"Outlook cannot log on.  Verify you are connected to the network and are using the proper server and mailbox name.  The Microsoft Exchange information service in your profile is missing required information.  Modify your profile to ensure that you are using the correct Microsoft Exchange information service."

What do I need to do to fix this?  Do I need to delete the profile and recreate it from scratch on each client PC?
I have one that has me stumped. A new customer has a DC and an Exchange 2016 server. Everything has been working fine until yesterday. Something happened and the server now will not let any of the Outlook clients connect. I can connect through OWA but I cannot send or receive emails. When trying to send, I get the You don't have permission to perform this action. Everything looks normal in the EAC. In the Event logs I am getting the 9041 which from reading on it points to DNS but the only DNS entry in the NIC configuration is the DC. Needless to say the customer is anxious to get email back up. Any ideas?
Good morning,

I have been naded an unusual issue, at least in my experience.

We have extremely important emails being sent from the UK via an MPLS setup, and they are using Private DNS entries. Our SPam and Email servers require rDNS or the emails are blocked. We whitelisted and IP address for them yesterday but that did not seem to help.

This has been escalated to top priority as these emails are for our CEO and COO. What can I do from my end to ensure that the emails can be received and delievered?

I have about four hours to correct this as the senders are on UK time and I am on EST time, so if anyne can help me I would be most gratefull.

We have a hosted server with an ssl certificate which we can access externally but on the wifi (dns external) we cannot access the hosted server. With the wifi and the hosted server are on different subnets behind the same firewall. Does anyone have any suggestions how we can overcome this issue?
I have a domain name registered with email hosting from Provider 1. I have a website built using Wix (Provider 2) and need to link the domain/pages at Wix to the registered domain.

What settings at Wix and at Provider 1 are required to make the above work?
I have

Exchange 2010 SP3 on Windows 2008r2 -  4 servers (2 CASHUB + 2 MBX).
Internal clients are using NLB called excasarray.domain.com pointing to DAG
Domain name has other DNS records internally referring to the excasarray.domain.com.  

As we added Exchange 2016 servers (RYEX01 & RYEX02) on the existing organization and migrated few pilot users for testing.  The issue is purely for the internal outlook users. After we migrate the users are getting certificate prompt of new exchange server which has only exchange server hostname and fqdn in the certificate. Hence it is throwing certificate prompt for all users stating the new certificate does not match with the other SAN names. We have added new DNS A record for autodiscover and webmail.domain.com. For external users access owa has no issue. But for the outlook users it is prompting for certificate. What i am missing here. Here are the output from virtual directories.  We want a solution to avoid certificate prompt for the user before we migrate the mailbox. Also we have public certificate applied on the old server and exported pfx file and iimported to the new server. Appreciate your help on the same.

[PS] C:\>Get-ActiveSyncVirtualDirectory -ADPropertiesOnly | fl Identity, *lurl*, *method*
Identity                      : RYCASHUB01\Microsoft-Server-ActiveSync (Default Web Site)
InternalUrl                   : https://rycashub01.domain.com/Microsoft-Server-ActiveSync
ExternalUrl                   : 

Open in new window

We have 3 DC's:
DC1, DC2, and DC3 for BigNet.Big.Ten.Edu (suppose to be visible just to Domain computers and servers)
and 2 NameServers:
 NS1.BigNet.Big.Ten.Edu and NS2.BigNet.Big.Ten.Edu
(We have control of the BigNet and Big levels of the domain... We don't have control of the Ten.Edu level)

After clearing out many DNS errors due to old/obsolete domain controllers that were found in the records (we had very slow logins),
I'm down to trying to isolate DC3 from showing up as a nameserver publically (as it is firewalled off to all except the Nameservers and Domain attached computers).
I'm in need of guidance in tracking down what we have set wrong.

NFR key for Veeam Backup for Microsoft Office 365
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

A client of ours is still sitting at "Windows Server 2003" for both the "domain and forest" functional levels. They only have 1 x 2008 member server with the rest of the member servers being Server 2012 and Server 2012 R2 editions.

We are having SYSVOL replication issues (I believe that it is still trying to use FRS versus using DFS Replication as it should be. We are also having DNS issues that we believe may be related to this as well.

I want to raise both the domain and forest functional levels, is there a specific order that these need to be done in? Is there a reboot of any kind required? Services that need to be restarted?

I haven't done this in several years so any suggestions are greatly appreciated.

Trying to move away from the &%$#$-ing 2008 SBS & yet another issue rears its ugly head.
When trying to run some of the pending updates, true to form, it rebooted & never did get to the desktop. I restored from a backup, but since then, network shares weren't available. They showed up with the red X on them & when double clicking, I'm getting the message;
\\Server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Logon failure:The target account name is incorrect.
Permissions haven't changed & name is correct, as has been the case since it was installed.  
I can ping the server by name or IP without problems.
If I go to map network drive, as soon as I select the server, I get that same message. But, if I put \\\share it maps the drive, no problem. Now, since I'm in the process of replacing this, I just re-created the shares on one of my new & improved servers, remapped everyone to those & all is well & I am only including all this, as it may lead to a solution my to bigger problem.
My bigger problem is when someone is using the remote desktop server (2008 R2) & tries to open outlook, a dialog box pops up,
Connecting to mailserver.mydomain.local, along with username (domainname\username) & a password box.
Entering password doesn't work, so Outlook never opens.
A few other things to consider as a possibility here, that version of outlook…
Hi.  I have spf record quesiton.  My mail is hosted by zoho mail.  I have no issues there.  But I have an AS400/iSeries that I am sending out emails nightly to customers with shipping info.   For example those emails are coming from S103jmr4.xxx.com (xxx being our domain name).  The idea I believe is to add an spf record with that special name in it so that people will receive those emails, but I want to make sure that people keep receiving the normal mail.    I used an spf builder to create a record using the S103jmr4.xxx.com.  But does that spf need to include info about the zoho mail server too?
Here is the spf record created.
xxx.com.  IN TXT "v=spf1 mx ptr a:s103jmr4.xxx.com ?all"

Basic Requirement for domain network ?
Hi there,
In our Internet accounting system users redirected to hotspot login page (based on Mikrotik CCR1036 12G 4S and installed a star SSL cetificate) and when there is a congestion in the logon (more that 500 users attempt simultaneously,) many of users encounters errors such as "The web page is not available" or "SSL connection error".
In that time, DNS server (Bind9 on Ubuntu 16.04.2 server) cannot respond to nslookup of domain name of hotspot page (internet.xxx.yyy) in a troubled system (has time out to respond query). I think that there is a limitation on how many queries that it can respond.

I would appreciate to give me guidance and tips.

Best Regards
My home Wi-Fi can't access certain websites and would forever load until it throws up an error state. When I'm connected via ethernet, it works fine, so I know the Wi-Fi has issues. I also want to add that my printer normally prints via Wi-Fi and lately it hasn't been connecting. I'm having to hardwire my printer to my Macbook.

  • The devices I'm using are Macbook and Android phone.
  • This problem started roughly three months ago. No changes have been made to my Wi-Fi (that I know of).
  • I tried changing the DNS. It worked for a day but now the problem continues to exist.
  • I've reset the modem/router.
  • I've tried accessing aforementioned websites on different browsers. Same problem.






The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.