Mailing Issues - DN ---Need Help urgently
yusman
Our users could emails send to users in the domain nkfs.org but their side could not send their emails to us.
They received a bounce back error which I have shown below; both mail servers did not make any configuration, so are both ISPs which i have contacted them.
Error Mg:
> The original message was received at Wed, 7 Jan 2004 10:32:40 +0800
> from [10.60.90.13]
>> ----- The following addresses had permanent fatal errors -----
><ann...@ppsjob.com.sg>>> ----- Transcript of session follows -----
><ann...@ppsjob.com.sg>... Deferred: Connection reset by
exchgsvr.ppsjob.com.sg.
> Message could not be delivered for 5 days
> Message will be deleted from queue
I have contacted the ISPs involved and gotten the IP to resolve the DNs. However this problem still remains.
Are the faults w my DNS or my Exchange server?
sharad
I just typed a test message with telnet, to your server
the message is sent to ann...@ppsjob.com.sg.
The message went through without any problem.
I seems like after you asked the ISP to correct the record, other
names server took their time for update, and now it is working.
Some people may still get error, but it will get solved in some hours.
Sharad
"yusman" <anon...@discussions.microsoft.com> wrote in message
news:BB75EDA0-C117-41DD...@microsoft.com...
yusman
one issue which i felt might be the problem is the multiple ip i have on my server... it was originally on my exchgsvr and everything work fine until i change my ISP then i start to encounter a lot of problem. Is there any issue if i remove exchgsvr host of 61.14.82.51 and 52 in my DNS??? is that the problem that why DNS report say there are multiple mail servers.
----- sharad wrote: -----
sharad
ppsjob.com.sg, ns0.ppsjob.com.sg, ns1.ppsjob.com.sg, ns2.ppsjob.com.sg,
all these DNS servers, you are hosting yourself, or are they hosted by your
ISP?
There are so many multiple records!! Please see below the results I got when
I tried to get your MX recrods.
-------------------------------------------------------
Non-authoritative answer:
ppsjob.com.sg MX preference = 10, mail exchanger = exchgsvr.ppsjob.com.sg
ppsjob.com.sg MX preference = 20, mail exchanger = exchgsvr.ppsjob.com.sg
ppsjob.com.sg MX preference = 30, mail exchanger = exchgsvr.ppsjob.com.sg
ppsjob.com.sg MX preference = 40, mail exchanger = exchgsvr.ppsjob.com.sg
exchgsvr.ppsjob.com.sg internet address = 61.14.82.52
exchgsvr.ppsjob.com.sg internet address = 61.14.82.50
exchgsvr.ppsjob.com.sg internet address = 61.14.82.51
exchgsvr.ppsjob.com.sg internet address = 61.14.82.52
exchgsvr.ppsjob.com.sg internet address = 61.14.82.50
exchgsvr.ppsjob.com.sg internet address = 61.14.82.51
exchgsvr.ppsjob.com.sg internet address = 61.14.82.52
exchgsvr.ppsjob.com.sg internet address = 61.14.82.50
exchgsvr.ppsjob.com.sg internet address = 61.14.82.51
exchgsvr.ppsjob.com.sg internet address = 61.14.82.52
exchgsvr.ppsjob.com.sg internet address = 61.14.82.50
exchgsvr.ppsjob.com.sg internet address = 61.14.82.51
------------------------------------------------------
1) 4 MX recrods with same host names "exchgsvr" !
Remove 3, keep only 1, with preference 10.
Above is not a way to have multiple MX recrod for
back up purspose! But you do not have a backup mail server, as it appears
so,
just keep only 1 MX recrod.
2) multiple host recrods, pointing to 3 different IP addresses, 3 times!
Remove all and keep only one recrod 'exchgsvr' pointing to only 1
IP address, of the server where you run the Exchange server.
Becuase all the 3 IP addresses from 61.14.82.50 to 61.14.82.52 are from the
same
ISP, and if the ISP link fails, you will not have any of these IP, so what
is the purpose
of having same host recrod, to all 3 IP address?
If at all you want MX recrod resolving to all 3 IP addresses (whatever the
reason
for this), then above is not the way to do it.
You will have to first create, another 2 host records, eg. exchgsvr1 &
exchgsvr2
each pointing to one of the remaining 3 IP addresses (and not the same IP
addresses, )
e.g. exchgsvr1 - 61.14.82.51 & exchgsvr2 - 61.14.82.52 (you already have
exchgsvr - 61.14.82.50)
Then add MX records, for exchgsvr1 and exchsvr2.
3) All your names server are too slow, ns1 and ns2 were not reachable.
exchgsvr.ppsjob.com.sg - SOA expires after time is 600 S (just 10 minutes!)
your secondary DNS can not update with such a low value, keep it 1 DAY
atleast. SOA, Min. TTL is 10 seconds, which is also too low, make it 1
Hour atleast.
4) Why so many names server entries, with the domain registrar? If you are
not
really going to run all these 4 names server, keep only 2 entries, Pirmary
and
Secondary (I think all domain regstrars require at least two.)
Sharad
"yusman" <anon...@discussions.microsoft.com> wrote in message
news:B40E55C3-9C9C-4F1F...@microsoft.com...
Jonathan de Boyne Pollard
Your Exchange server is aborting the SMTP/TCP transaction for some
reason. This is not a DNS problem.
Yusman
Sharad, I took your advice so here is my update:
All domains hosted by my company. My company got 3 domains, that means x...@ppsjob.com.sg , x...@synergi.com.sg and x...@staffhub.com will be send to the same user's mailbox and all this 3 domains have their own websites all under the same server. So do i need to have exchgsvr1 and exchgsvr2 pointing to the 2 addition domains(synergi.com.sg and staffhub.com) or i jus delete exchgsvr host record of 61.14.82.51 and .52 (and keep 61.14.82.50) and the email of x...@synergi.com.sg and x...@staffhub.com will still be sent to the same mailbox.
do i need to make any changes to my ns0(IP:61.14.82.50), ns1(IP:61.14.82.51) and ns2(IP:61.14.82.52) host record?
I also notice that there are one "Start of Authority" and four "Name Server" pointing to exchgsvr.com.sg, ns0ppsjob.com.sg, ns1ppsjob.com.sg and ns2ppsjob.com.sg. can advise me what are these for and whether the SOA changes are to made to all the records?
BTW i already deleted the MX record with preference 20, 30, 40 and notice that there is no more Duplicate MX record. But 2 of my parent name server 61.14.82.51 and 52
did not respond and also there is a failure in connecting to my Mail Server.
http://www.dnsreport.com/tools/dnsreport.ch?domain=ppsjob.com.sg
Jerryl
Yusman is helping me to post the question previously.
I am new to on server issue...so pardon me for asking some common questions.
I have no problem sending and receiving from other domains, only discover 2 domains got problem sending emails to me and they are from the same ISP, i check with the domain administrator and their ISP and mine that they did not made any changes
I was able to receive email from nkfs.org only until recently. Dont know what has gone wrong.
sharad
these are hosted by your ISP. You run exchange server
only on one machine, that has IP address of 61.14.82.50.
2. It seems in the exchange server, you have these 3 registered domain
(only 1 exchanger server with 3 domains.)
Are above two points correct? If yes, then
you need to ask your ISP to add Host A recrod
'exchgsrvr' for each domains.. 'synergy.com.sg' and 'staffhub.com' ,
in the respective forward zones, both resolving to IP 61.14.82.50
then add MX record for them.
In short there must be MX records
exchgsrvr.synergy.com and exchg.srvr.staffhub.com
both resolving to IP 61.14.82.50.
Sharad
"Jerryl" <anon...@discussions.microsoft.com> wrote in message
news:BCE9DDCE-75C6-436F...@microsoft.com...
Jonathan de Boyne Pollard
Remember: The problem symptoms that you actually described in your first
message had _nothing whatever_ to do with DNS service.
Y> So do i need to have exchgsvr1 and exchgsvr2 pointing to the 2
Y> addition domains(synergi.com.sg and staffhub.com) or i jus
Y> delete exchgsvr host record of 61.14.82.51 and .52 (and keep
Y> 61.14.82.50) and the email of x...@synergi.com.sg and
Y> x...@staffhub.com will still be sent to the same mailbox. do i
Y> need to make any changes to my ns0(IP:61.14.82.50),
Y> ns1(IP:61.14.82.51) and ns2(IP:61.14.82.52) host record?
The way to approach this is to be methodical. Start with the basics:
* You have three domains, "ppsjob.com.sg.", "synergi.com.sg.", and
"staffhub.com.".
* You want the content DNS service for those domains (and their subdomains) to
be provided by your (one) content DNS server, listening on 61.14.82.50.
* You want the SMTP Relay service for mailboxes in those domains to be
provided by your Exchange server, also listening on 61.14.82.50.
Therefore:
* Create "MX" resource record sets for each of those domains (removing all
other "MX" resource records):
ppsjob.com.sg. IN MX 86400 10 a.mx.ppsjob.com.sg.
synergi.com.sg. IN MX 86400 10 a.mx.synergi.com.sg.
staffhub.com. IN MX 86400 10 a.mx.staffhub.com.
and matching "A" resource record sets:
a.mx.ppsjob.com.sg. IN A 86400 61.14.82.50
a.mx.synergi.com.sg. IN A 86400 61.14.82.50
a.mx.staffhub.com. IN A 86400 61.14.82.50
Note #1: The intermediate domain names (a) don't have to be the same as one
another even though they will be referencing the same machine, (b) don't have
to be the "usual" name of the machine, and (c) should be subdomains of their
respective domains.
Note #2: Your current choice of TTL on all of your resource record sets, 10
seconds, is far too short. Are your data really likely to fluctuate every 10
seconds ? I strongly suspect that your data will remain static for days or
even months at a time, and will not need to be changed at less then a day's
notice.
Note #3: You must also configure your Exchange server to accept mail addressed
to mailboxes in those three domains.
* Create "NS" resource record sets for each of those domains (removing all
other "NS" resource records):
ppsjob.com.sg. IN NS 86400 a.ns.ppsjob.com.sg.
synergi.com.sg. IN NS 86400 a.ns.synergi.com.sg.
staffhub.com. IN NS 86400 a.ns.staffhub.com.
and matching "A" resource record sets:
a.ns.ppsjob.com.sg. IN A 86400 61.14.82.50
a.ns.synergi.com.sg. IN A 86400 61.14.82.50
a.ns.staffhub.com. IN A 86400 61.14.82.50
Note #1: The intermediate domain names (a) don't have to be the same as one
another even though they will be referencing the same machine, (b) don't have
to be the "usual" name of the machine, and (c) should be subdomains of their
respective domains. Your existing "staffhub.com." delegation is effectively
glueless because the intermediate domain name that it uses is not only _not_ a
subdomain of "staffhub.com." it isn't even a subdomain of "com.".
Note #2: Your current choice of TTL on all of your resource record sets, 10
seconds, is, again, far too short. The superdomain content DNS servers are
using TTL values of 1 day. Do so too.
Note #3: It might be a good idea for you to pay a DNS hosting service to
publish your DNS data from a second (and possibly a third) content DNS server
on another IP address as well. In which case you would add some more resource
records:
ppsjob.com.sg. IN NS 86400 b.ns.ppsjob.com.sg.
ppsjob.com.sg. IN NS 86400 c.ns.ppsjob.com.sg.
b.ns.ppsjob.com.sg. IN A 86400 10.53.0.1
c.ns.ppsjob.com.sg. IN A 86400 10.53.1.1
synergi.com.sg. IN NS 86400 b.ns.synergi.com.sg.
synergi.com.sg. IN NS 86400 c.ns.synergi.com.sg.
b.ns.synergi.com.sg. IN A 86400 10.53.0.1
c.ns.synergi.com.sg. IN A 86400 10.53.1.1
staffhub.com. IN NS 86400 b.ns.staffhub.com.
staffhub.com. IN NS 86400 c.ns.staffhub.com.
b.ns.staffhub.com. IN A 86400 10.53.0.1
c.ns.staffhub.com. IN A 86400 10.53.1.1
Don't be tempted to use the hosting service's name for its content DNS server
as the intermediate domain names in your delegations. Doing so can easily, and
will very probably (unless you know exactly what you are doing), result in more
gluelessness.
* Register all of these delegations (as "DOMAIN" and "HOST" records) via your
appropriate "com." and "com.sg." registrars, using the same names as in your
published DNS data. (For example: Register, via your chosen "com." registrar,
a "HOST" record for "a.ns.staffhub.com.", mapping to 61.14.82.50, and a
"DOMAIN" record for "staffhub.com.", mapping to "a.ns.staffhub.com.".)
If you need to give your Exchange server names for humans to use, _then_ you
will add "A" resource record sets for "exchgsrv.ppsjob.com.sg." and whatever
else you may choose. But creating human-usable names is _separate_ from what
you do to create delegation information and SMTP Relay server information for
your domains.