Hi,
as of this morning (I think) I have problems connecting to various
website that use Akamai from my Bitfolk VPS.
For example:
e6203.b.akamaiedge.net.
a1723.g.akamai.net.
a1723.g.akamai.net.
I can reach those servers (on port 80) without issues from another UK
server (behind an business ADSL connection), but from Bitfolk the
connection times out.
It's probably not something Andy/Bitfolk can do much about, but I
thought I'd mention it just in case (or in case this is something
specific to my VPS).
Martijn.
Hello!
I'm coming around to the idea of running my own mail servers again and
closing down my google apps accounts, try and free myself from our googley
overlord a little bit :)
Last time I did this I remember it being a pita to maintain. Can anyone
recommend some reading for someone who hasn't maintained a mail server for
about 7 years to catch up please?
Thank!
-Matt Daubney
As ever, I'd quite like someone else to do the Wheezy to Jessie upgrade
first :)
The one thing I know I have to watch out for is that the change from
Apache 2.2 to 2.4 involves a change in the authentication modules for
websites that use it. I have it on \wp-admin for WordPress websites as
that stops the bots from bothering WordPress itself...
Ian
Hi,
Assume that:
1) You're a user of BitFolk's secondary DNS service.
2) One or more of your zones have been unreachable from our
secondary servers for so long that they have expired.
How long would you expect BitFolk to continue serving SERVFAIL for
your zone(s) before removing them from the configuration (and
thereafter serving NOERROR/REFUSED as for any name they're not
authoritative for)?
If any of you use other similar services where you provide the
primary DNS server, what do they do in that circumstance?
Is there a difference in behaviour in typical Internet protocols
that encounter SERVFAIL vs NOERROR? e.g. would a mail server
consider SERVFAIL to be a temporary failure but NOERROR to be a
permanent one?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
