|
#11
|
||||
|
||||
|
Is your server running active directory? If so...should only have 192.168.2.20 as the only DNS server being handed out. You set the OpenDNS servers in the "Forwarding" section of your DNS MMC....so your DC's DNS looks to those for answers. All DNS requests should flow through your DCs DNS. If workstations that are clients in active directory use other DNS sources, their connection to AD will be broken.
__________________
Resident "Geek on a Harley" doing IT in Southeast Connecticut http://www.dynamic-alliance.com/ https://www.facebook.com/YeOldeStonecat |
|
#12
|
|||
|
|||
|
Ok, I removed all the dns servers from that screen except 192.168.2.20 and the forwarders section of the dns mmc now has the following
192.168.2.1 208.67.222.222 (opendns) 208.67.220.220 (opendns) 75.75.75.75 (comcast) 75.75.76.76 (comcast) I'm still not having any luck EDIT: it appears my comcast modem is the culprit, as soon as I remove 192.168.2.1 from the forwarders list my android works fine thanks guys!
__________________
Twin County Computers LLC | Twin County Security LLC
Computer Sales & Repair, Networking, Web Design Burglar Alarms, Fire Alarms, Video Surveillance PO Box 456 Woodlawn, Va 24381 30 Melrose Ln Galax, Va |
|
#13
|
||||
|
||||
|
Probably was getting checked first....and it's the quickest to reply.
FYI...all of my Windows Server setups at client...their DNS forwarders are only OpenDNS. If you add extra DNS servers...you may loose some of the benefits of OpenDNS blocking of known malware sites...so you lose the protection (since other DNS servers will probably reply with the actual address).
__________________
Resident "Geek on a Harley" doing IT in Southeast Connecticut http://www.dynamic-alliance.com/ https://www.facebook.com/YeOldeStonecat |
![]() |
| Thread Tools | |
| Display Modes | |
|
|