• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

DNS Problems

S

SKiTLz

2[H]4U
Joined
Aug 3, 2003
Messages
2,664
You guys have any ideas on this?

I have two 2008 R2 DC's that are DNS servers. Both are configured to use the Root Servers for recurssion.

I've had a few in house complaints of mail not getting delivered to a few people. So i check the queue and sure enough those domains aren't resolving in Exchange. If i drop to a shell they still don't resolve "DNS request timed out". The weird thing is this is for 3-4 domains. Every other domain (Internal & External) works perfectly fine.

The domains in question also resolve fine using another DNS server like 4.2.2.2 or my home.

I've tried clearing cache, verifying DNS settings on DC01 and DC02. It just makes no sense why these few domains won't resolve yet everything else will.

Any ideas?
 
I would suggest reviewing your TCP/IP stacks on the server and removing any external DNS listings.

Lets say DC01 is 192.168.0.5 and DC02 is 192.168.0.6 your DNS information should look like this

DC01 primary DNS 192.168.0.5, secondary 192.168.0.6
DC02 would be .6, .5

In DNS Server, make sure no internal servers are listed as forwarders, and suggest using 4.2.2.2 as the tertiary server (primary and secondary being from your ISP).

Would also suggest (if not already done) to setup the DNS servers as Primary and Secondary, if they are currently both Primary zones.. even with Zone Transfers it can get ugly.
 
http://dnsresolvers.com/

The EasyDNS open resolvers are:

cache1.dnsresolvers.com -> 205.210.42.205
cache2.dnsresolvers.com -> 64.68.200.200


Set those as DNS forwarder on both DCs (or other open resolvers of your choosing, EasyDNS is my fav). Then clear the DNS server cache, then do an ipconfig /flushdns on any affected servers. Fixed.
 
You must log in or register to reply here.
Back
Top