Unable to bind to the destination server in DNS - Please help

  • Thread starter Thread starter Mr555
  • Start date Start date
M

Mr555

Hi Everyone , Microsoft expert

We have problem sent e-mail to some domain from time to
time, I can telnet into their mail Server, but I get the
follow error message.

Message delivery to the remote domain 'agal.gov.au' failed
for the following reason: Unable to bind to the
destination server in DNS.

If you have suggestion or any solution for this will be
much appreciated.

Thank in advance
 
In
Mr555 said:
Hi Everyone , Microsoft expert

We have problem sent e-mail to some domain from time to
time, I can telnet into their mail Server, but I get the
follow error message.

Message delivery to the remote domain 'agal.gov.au' failed
for the following reason: Unable to bind to the
destination server in DNS.

If you have suggestion or any solution for this will be
much appreciated.

Thank in advance
Click to expand...

Interesting error. What Event log errors do you have (post the Event ID #s).

It could be their server and they don't have an MX record created. I tried
to look up that domain name you provided. Now if the name you provided is
accurate (and not a munge), then this domain does not have an MX record
created. Look here:

C:\nslookup
Default Server: ponyexpress.bandwidthpros.com
Address: 208.47.39.10
set type=mx
agal.gov.au
Click to expand...
Server: ponyexpress.bandwidthpros.com
Address: 208.47.39.10

DNS request timed out.
timeout was 2 seconds.
*** Request to ponyexpress.bandwidthpros.com timed-out

Also, take a look here:
http://www.experts-exchange.com/Networking/Microsoft_Network/Q_20568892.html

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
AF> It could be their server and they don't have an MX
AF> record created.

They have. It just takes longer than 2 seconds to resolve a query
for it. (It just took 18 seconds for me.) The 2 second timeout
in your test using "nslookup" was simply too short.

[C:\]timer & dnsgetmx agal.gov.au. & timer
Timer 1 started: 2003-11-28 15:08:47 +0000
202.125.8.25
Timer 1 stopped: 2003-11-28 15:09:05 +0000 elapsed: 00:00:18
[C:\]

Lack of an "MX" resource record set (and concomitant "A" resource
record sets) is not the problem.

[C:\]dnsqry mx agal.gov.au. | grep /b/u Answer:
Answer: agal.gov.au. IN MX 43067 10 canberra.securenet.com.au.
[C:\]dnsqry a canberra.securenet.com.au. | grep /b/u Answer:
Answer: canberra.securenet.com.au. IN A 593 202.125.8.25
[C:\]

The lengthy query resolution is partly because the "agal.gov.au."
delegation is messed up. The "gov.au." content DNS servers delegate
to three "agal.gov.au." content DNS servers (203.13.26.17,
147.211.53.240, and 203.0.101.100) only one of which (203.0.101.100)
actually responds to DNS queries.
 
This is interesting

I got their MX record. I telnet to their Server and sent a
test e-mail to 2 users, they both received my e-mail and
replied to me. This looks like is exchange issue.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>telnet

C:\>nslookup -q=mx agal.gov.au
Server: alien.xtra.co.nz
Address: 202.27.184.3

agal.gov.au MX preference = 10, mail exchanger =
canberra.securenet.com.au
agal.gov.au nameserver = ns.au.csc.net
ns.au.csc.net internet address = 203.0.101.100
 
In
This is interesting

I got their MX record. I telnet to their Server and sent a
test e-mail to 2 users, they both received my e-mail and
replied to me. This looks like is exchange issue.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>telnet

C:\>nslookup -q=mx agal.gov.au
Server: alien.xtra.co.nz
Address: 202.27.184.3

agal.gov.au MX preference = 10, mail exchanger =
canberra.securenet.com.au
agal.gov.au nameserver = ns.au.csc.net
ns.au.csc.net internet address = 203.0.101.100
Click to expand...


Very well,then if it's an Exchange issue, did you read this article I
previously provided?

http://www.experts-exchange.com/Networking/Microsoft_Network/Q_20568892.html


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jonathan de Boyne Pollard said:
It could be their server and they don't have an MX
record created.
Click to expand...

They have. It just takes longer than 2 seconds to resolve a query
for it. (It just took 18 seconds for me.) The 2 second timeout
in your test using "nslookup" was simply too short.

[C:\]timer & dnsgetmx agal.gov.au. & timer
Timer 1 started: 2003-11-28 15:08:47 +0000
202.125.8.25
Timer 1 stopped: 2003-11-28 15:09:05 +0000 elapsed: 00:00:18
[C:\]

Lack of an "MX" resource record set (and concomitant "A" resource
record sets) is not the problem.

[C:\]dnsqry mx agal.gov.au. | grep /b/u Answer:
Answer: agal.gov.au. IN MX 43067 10 canberra.securenet.com.au.
[C:\]dnsqry a canberra.securenet.com.au. | grep /b/u Answer:
Answer: canberra.securenet.com.au. IN A 593 202.125.8.25
[C:\]

The lengthy query resolution is partly because the "agal.gov.au."
delegation is messed up. The "gov.au." content DNS servers delegate
to three "agal.gov.au." content DNS servers (203.13.26.17,
147.211.53.240, and 203.0.101.100) only one of which (203.0.101.100)
actually responds to DNS queries.
Click to expand...

I see. Thanks.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top