resolve - DNS lookup failing -
i have primary , secondary domain controller use our dns servers. users getting mixed results accessing websites. work fine, others giving error:
network access message: website cannot found explanation: ip address website requested not found. result, not possible access site.
for example, mcmaster.com not work. if run nslookup primary dc:
c:\users\administrator>nslookup mcmaster.com server: dc.mydomain.local address: 10.1.1.35 non-authoritative answer: name: mcmaster.com address: 209.64.25.230
all looks well, when run nslookup
www. prepended address:
c:\users\administrator>nslookup www.mcmaster.com server: dc.mydomain.local address: 10.1.1.35 dns request timed out. timeout 2 seconds. dns request timed out. timeout 2 seconds. *** request dc.mydomain.local timed-out
running nslookup www.mcmaster.com
dc gives different error:
*** backupdc.mydomain.local can't find www.mcmaster.com: server failed
i think mcmaster.com resolves www.mcmaster.com, results in user not being able access site. ideas how can troubleshoot this?
i ran nslookup system @ work , got following response:
server: whatever address: xxx.xxx.xxx.xxx non-authoritative answer: name: mcmaster.com address: 209.64.25.230 server: whatever address: xxx.xxx.xxx.xxx non-authoritative answer: name: a1843.b.akamai.net addresses: 23.66.232.17 23.66.232.26 aliases: www.mcmaster.com www.mcmaster.com.edgesuite.net
my initial thought whoever owns dns mcmaster didn't have www valid response. know forward requests www.whateverdomainirun.com whateverdomainirun.com, but, seeing different dns 2 surprised me.
when navigate http://mcmaster.com forwarded www. when run tracert on mcmaster.com fails destination net unreachable. looks me company has put site in akamai's hands , either that's recent local dns servers haven't updated , try flushing cache , doing again, or, in way you're blocking requests akamai reason on firewall.
best , quick guess , may wildly wrong :).
Comments
Post a Comment