Tag Info

Hot answers tagged

7

As a best practice, you should be running AD DS and AD-Integrated DNS zones (ADI zones) on the same server. This is because the DNS records in ADI zones are replicated using AD DS replication and are stored in the directory, rather than using things like a zone transfer to get records across multiple DNS servers. If you want to use ADI zones for your ...


3

You say the IP has changed, which sounds like you may be using DHCP to assign addresses? Check the DHCP log files C:\Windows\system32\dhcp. Use the time and the IP to find the MAC address, then use your inventory system to track down that asset. https://technet.microsoft.com/en-us/library/dd183591%28v=ws.10%29.aspx


2

The first of the two diagrams in your question is incorrect. Root servers don't send queries to other servers. If the root servers did in fact forward queries like shown in that diagram the DNS system would be a lot more vulnerable to DoS attacks than it really is. The second diagram is mostly correct but too simplified to show you the recursive nature of ...


2

You have to setup a TXT record for dkim._domainkey.gamerbasecamp.com, while you are doing test from dkim._domainkey.gamerbasecamp.info.


1

You can create a daisy-chain of rules with (potentially) limitless length. here's a 3 server layout: FQDN is mapped to a failover policy with Primary and Secondary where Primary is Server1 and secondary is another FQDN (FQDN2) this FQDN2 has a failover policy of its own with Primary pointing to Server2 and Secondary pointing to Server3. In total you'll ...


1

Connection Reset is a server response and is not likely a firewall issue. What is occurring is during the three way handshake a reset is being sent in response instead of a SYN ACK. This is notifying you and your browser that the web server application (IIS/apache etc.) is not accepting connections. This means there is an actual issue with the web server ...


1

Resolution was to access the system logs of the machine which currently had that IP. It was an OSX machine and I was able to grep 'IP ADDRESS' /var/log/* /dev/null to find a log file which held historical IP information. I found that it was held in /var/log/daily.out and I was able to confirm the machine which currently held that IP had also had the same IP ...



Only top voted, non community-wiki answers of a minimum length are eligible