On 2/11/2015 2:07 p.m., Eliezer Croitoru wrote:
> Hey Robert,
>
> It is really unclear what you need or want(at least to me).
> The basic way that the routing world works is that if you try to access
> an IPV4 address is by using the IPV4 routing world.
> It means that you need to use an IPV4 addr
Hi!Sorry for my long answer. I checked I have a normal synchronization with my Domain Controllers of Active Directory. I use chronyc for synchronization ntp. Please look below messages:# chronyc sources210 Number of sources = 3MS Name/IP address Stratum Poll Reach LastRx Last sample
Hey Robert,
It is really unclear what you need or want(at least to me).
The basic way that the routing world works is that if you try to access
an IPV4 address is by using the IPV4 routing world.
It means that you need to use an IPV4 address to access IPV4 resources
or networks.
I remember ta
Also noticed the typo in my backend config
http_port 127.0.01:400${process_number}
should have been
http_port 127.0.0.1:400${process_number}
However this change did not help with getting cached results, still goes
direct.
Mike Hodgkinson
Internal Support Engineer
Mobile +64 21 754 339
Phone
Thank you Amos, I was pretty brain drained by the time I posted so please
excuse my pasting slip up.
I tried adding no-netdb-exchange and no-digest to the cache_peer lines,
the first one eliminated the forward loop warnings but I am still
experiencing the first request coming from the cache an
I have an IPv6 outgoing address setup and it works correctly but when I access
a website that has an IPv4 address it uses the main IP of the server, is there
any way to disable the use of the main IPv4 address of the server and only use
the IPv6 outgoing address? I have tried to add only IPv6 DN
