What do you mean you changed a DC to backup? Is DNS still on it? Is that
where you are getting dns from? If you removed AD from a DNS DC, then DNS will
be flakey if it runs at all.
Try random browsing from the toaster and see how well DNS performs.
-Original Message-
From: Kent
Kent Busbee wrote:
Ok, forgive me b/c I am trying to go through gmail to get this out
more quickly
the queue is 200+ and growing.
I believe the emails are going out very slowly. My first post was at
10:48 AM and did not show up until 2:29 PM. Thanks for the testing/
help all.
My MX
That usually means Yahoo or another ISP is deferring your connection due to
reported abuse, or you have exceeded your allow connection in each session.
This is common with Yahoo, if it extend more then two days, your on there
Blacklist and have to get removed by feeling out the form on there
: [qmailtoaster] Re: bandwidth hog
That usually means Yahoo or another ISP is deferring your connection due to
reported abuse, or you have exceeded your allow connection in each session.
This is common with Yahoo, if it extend more then two days, your on there
Blacklist and have to get removed by feeling out
OK, moving any FSMO roles won't have anything to do with your problem then.
The Domain Naming master also doesn't have anything to do with DNS. It's
the central manager for your own AD domain and nothing on the outside. I
was concerned if you demoted a DC that you were getting DNS from.
Where
[r...@mail ~]# cat /etc/resolv.conf
search ncs-ad.northlakechristian.org
nameserver 192.168.1.5
nameserver 127.0.0.1
nameserver 192.168.1.254
nameserver 207.29.223.56
nameserver 207.29.223.58
[r...@mail ~]#
192.168.1.5 is my MS ncsw2k3 server
I don't think dns is the problem
It looks like I may
OK...
My queue is now down to 0.
I am writing from my server. Let's hope this goes through. What I need
to do is figure out what caused:
a) the server to eat all the bandwidth of our T1
b) what caused the queue to get so full and take so long to get out.
See response above; Kent Busbee
I'm on it. I'll let Kent report back the results of our findings.
Kent Busbee wrote:
OK...
My queue is now down to 0.
I am writing from my server. Let's hope this goes through. What I need
to do is figure out what caused:
a) the server to eat all the bandwidth of our T1
b) what caused the
