nocalerts
asked on
Some external domaine not resolving on new 2003 to 2008 migration.
We recently migrated from Server 2003 to 2008 DNS and DCs we are having a weird issue where paypal and it seems to only be paypal so far is unreachable or pingable. If I connect to our public Wireless network(outside our DMZ and using same link) it works fine. I have a feeling it may have something to do with Root hints or something but I don't know enough to troubleshoot. It's just weird that it is not for all sites. We are not using any forwarders.
Thanks in Advance
Thanks in Advance
BCipollone
Hmm I would flush the DNS and ARP tables. Are you able to ping either the host name or the IP seperately? Have you narrowed it down to your DNS server? Is it resolving the correct IP address?
ASKER
I will try restarting DNS and if that fixes it I'll try the Reg fix. Does anyone see a problem restarting the DNS service in the middle of the day is I have 2 Servers?
DNS takes a few seconds max to do a service restart. a few clients may get web page not found etc if they are real unlucky.
ASKER
Ok Thanks I'll let you know how it goes.
ASKER
No luck. I'll try in a few minutes incase something has to replicate. Any other ideas if it still doesn't work?
You have done the regfix?
ASKER
no not yet
ASKER
I will try that tonight
May sound dumb but did you create a forward zone for paypal?
On one of the machines where you can't access it do:
nslookup
set type=ns
paypal.com
(ensure the result is valid)
then:
server <any of the servers from the results above>
set type=a
<hostname you want to ping>
On one of the machines where you can't access it do:
nslookup
set type=ns
paypal.com
(ensure the result is valid)
then:
server <any of the servers from the results above>
set type=a
<hostname you want to ping>
IF it is the issue i posted about then WHEN you restart DNS it will seem to work, even though you havent done the reg fix. FOR A WHILE.
The whole point is its a known bug and a reboot/restart of DNS will fix it very short term.
The whole point is its a known bug and a reboot/restart of DNS will fix it very short term.
ASKER
restarting DNS services didn't fix the problem. So should I still try the reg fix?
ddiazp: I'm not sure what you mean by setup a forward zone. Shouldn't the root hints forward it correctly?
ddiazp: I'm not sure what you mean by setup a forward zone. Shouldn't the root hints forward it correctly?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, mine was a rather tricky question.
If you added a forward lookup zone for the domains you cant access then that would explain it. other than that, probably the other guys are onto something
If you added a forward lookup zone for the domains you cant access then that would explain it. other than that, probably the other guys are onto something
If it were me I would try disabling eDNS. It's an easy command line and does not require a server restart (although I would personally restart DNS). This has helped me numerous times on 2008 servers
http://support.microsoft.com/kb/832223
From an elevated command prompt, type the following and hit enter
dnscmd /config /enableednsprobles 0
NOTE: that is the number zero and not "O"
http://support.microsoft.com/kb/832223
From an elevated command prompt, type the following and hit enter
dnscmd /config /enableednsprobles 0
NOTE: that is the number zero and not "O"
ASKER
I fixed it by adding google's dns servers as a forwarder. (8.8.8.8) I would recomend setting that if you can. It made our page loads faster than I have ever seen them
Thanks everyone.
Thanks everyone.