Prev: Killing sent email before it finishes
Next: Removal of older java updates
From: Vgolfmaster on 12 Dec 2009 21:20
I don't truly know if this is a DNS issue, but when I open Internet Explorer
it sometimes tries to resolve the IP address of my home page and my favorites
and does not connect. Closing it and reopening IE normally corrects it, and
it then resolves the domain name and connects fine. I do not understand why
this only happens some of the time and why it seemingly fixes itself by
closing and reopening IE, without any other changes.

Does this sound like a DNS issues, or s security setting, or something else?
It does not happen with any other browsers, only IE.

Any suggestions would be appreciated.

Vgolfmaster

--
"Friends Don''t Let Friends Dial-Up"
From: Robert Aldwinckle on 12 Dec 2009 22:45

"Vgolfmaster" <Vgolfmaster(a)discussions.microsoft.com> wrote in message news:B681D789-5872-4948-BFA6-2AB680E14EC5(a)microsoft.com...
>I don't truly know if this is a DNS issue, but when I open Internet Explorer
> it sometimes tries to resolve the IP address of my home page and my favorites
> and does not connect. Closing it and reopening IE normally corrects it, and
> it then resolves the domain name and connects fine. I do not understand why
> this only happens some of the time and why it seemingly fixes itself by
> closing and reopening IE, without any other changes.
>

> Does this sound like a DNS issues, or s security setting, or something else?
> It does not happen with any other browsers, only IE.
>
> Any suggestions would be appreciated.


It could be DNS but you could eliminate that as a possibility by
first doing a ping -n 1 to get the lookup cached. Use ipconfig /displaydns
to prove that you have cached an A record (contains the IP address)
and whatever else it would need (e.g. any CNAME records to satisfy
a chain of aliases) and verify that the Time to Live of all those records
would be sufficient for you to let IE try to use them. You could also
prove that IE used the cache only and didn't do a real lookup by running
a packet trace such as WireShark or netmon; e.g. verify that the IP address
was used without another request to a DNS server being done.

Another way to eliminate a real lookup would be to add an entry
to your HOSTS file. Again, a trace could prove how effective
that was at bypassing your DNS server.


Good luck

Robert Aldwinckle
---


From: Vgolfmaster on 12 Dec 2009 23:37
Hi Robert,

Thanks for the reply, I did in fact just get done modifying the registry and
giving the highest priority to the HostsPriority, then 2nd priority to the
DomainNameSystem. After testing the hosts file with a few additions, I
identified that it was in fact giving priority there, and after replacing the
hosts file back to its original state, it now works fine.

Thanks much for the replay, if this problem returns I will look into the
rest of your suggestions.

Vgolfmaster
--
"Friends Don''t Let Friends Dial-Up"


"Robert Aldwinckle" wrote:

>
> "Vgolfmaster" <Vgolfmaster(a)discussions.microsoft.com> wrote in message news:B681D789-5872-4948-BFA6-2AB680E14EC5(a)microsoft.com...
> >I don't truly know if this is a DNS issue, but when I open Internet Explorer
> > it sometimes tries to resolve the IP address of my home page and my favorites
> > and does not connect. Closing it and reopening IE normally corrects it, and
> > it then resolves the domain name and connects fine. I do not understand why
> > this only happens some of the time and why it seemingly fixes itself by
> > closing and reopening IE, without any other changes.
> >
>
> > Does this sound like a DNS issues, or s security setting, or something else?
> > It does not happen with any other browsers, only IE.
> >
> > Any suggestions would be appreciated.
>
>
> It could be DNS but you could eliminate that as a possibility by
> first doing a ping -n 1 to get the lookup cached. Use ipconfig /displaydns
> to prove that you have cached an A record (contains the IP address)
> and whatever else it would need (e.g. any CNAME records to satisfy
> a chain of aliases) and verify that the Time to Live of all those records
> would be sufficient for you to let IE try to use them. You could also
> prove that IE used the cache only and didn't do a real lookup by running
> a packet trace such as WireShark or netmon; e.g. verify that the IP address
> was used without another request to a DNS server being done.
>
> Another way to eliminate a real lookup would be to add an entry
> to your HOSTS file. Again, a trace could prove how effective
> that was at bypassing your DNS server.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
> .
>
 | 
Pages: 1
Prev: Killing sent email before it finishes
Next: Removal of older java updates