R
Ray Von Geezer
Hi,
I'm looking for ideas on how to solve or workaround this issue, so any help would be appreciated. I think the actual problem is caused by public DNS servers which return placeholder IP addresses for unknown domains, rather than correctly reporting them as being unknown, but it's causing a lot of problems for our remote users.
The scenario is this. When domain-member laptops are not on the domain network, they can take anywhere between 5-30 minutes to login. This issue only occurs when the network they're connected to presents DNS servers which resolve unknown DNS hosts/domains to "placeholder" sites. Whilst Windows 7 laptops do also seem to suffer from this, login delays on those are at worst a couple of minutes, whereas the Windows XP machines are affected for much longer.
Maybe a bit more info will make it clearer
The AD namespace shares the external domain, and there are DNS records for the public domain, but obviously not for internal hosts (like DCs). So internally, the FQDNs of the domain controllers are "DC1.company.com", "DC2.company.com" etc.
When the laptop is connected to users home network, users can logon quickly (
I'm looking for ideas on how to solve or workaround this issue, so any help would be appreciated. I think the actual problem is caused by public DNS servers which return placeholder IP addresses for unknown domains, rather than correctly reporting them as being unknown, but it's causing a lot of problems for our remote users.
The scenario is this. When domain-member laptops are not on the domain network, they can take anywhere between 5-30 minutes to login. This issue only occurs when the network they're connected to presents DNS servers which resolve unknown DNS hosts/domains to "placeholder" sites. Whilst Windows 7 laptops do also seem to suffer from this, login delays on those are at worst a couple of minutes, whereas the Windows XP machines are affected for much longer.
Maybe a bit more info will make it clearer
The AD namespace shares the external domain, and there are DNS records for the public domain, but obviously not for internal hosts (like DCs). So internally, the FQDNs of the domain controllers are "DC1.company.com", "DC2.company.com" etc.
When the laptop is connected to users home network, users can logon quickly (
