|
|
|
Author
| Message |
|---|
|
|
The problems are with the DNS servers, not necessarily with the web server that hosts queenalice.com. During the outages, neither the primary nor secondary DNS responds. Both of these are on the same network (against recommendations in the internet standards documents) which suggests to me that it's a problem with the network rather than with the individual computers. I've noted down the IP address of the web server so, if there's another DNS outage, I'll investigate whether anything else on that network is reachable. My guess is that it won't be.
|
|
|
DNS is not the problem, the DNS server runs on the same server as the site, that's why it goes down at the same time.
I know it's bad practice, but having it setup this way has nothing to do with the outages.
Miguel
|
|
|
| miguel wrote: the DNS server runs on the same server as the site |
Are you sure?
$ host queenalice.com
queenalice.com has address 65.23.153.10
$ host -t NS queenalice.com
queenalice.com name server ns1.queenalice.com.
queenalice.com name server ns2.queenalice.com.
$ host ns1.queenalice.com
ns1.queenalice.com has address 65.23.153.15
$ host ns2.queenalice.com
ns2.queenalice.com has address 65.23.153.16 |
Is that one machine with three different IP addresses or three machines?
| having it setup this way has nothing to do with the outages. |
Agreed, though it does mean that the outages cause the rather confusing error message `host does not exist' rather than `host is not responding'.
|
|
|
Of course I'm sure. I setup this server myself.
|
|
|
OK, I believe you. 
|
| Previous 1 2 3 4 5 Next |
|
|
|
