| Author |
Message |
Guest
|
Posted:
Tue Dec 27, 2005 5:58 pm Post subject:
SMTP Server Name -- DNS |
|
|
We are about to migrate to Exchange 2003 from Exchange 5.5 (late we
know :)
We are testing out the SMTP to the internet and things are working
well, execpt for those sites that are doing REVERSE lookups on the
server names.
We have setup reverse lookup for our outbound severs as or normal name
space, but it seems when the messages are delivered, they are looking
up the active directory domain name (which naturally isnt on the
outside of our network), instead of the public name space name for the
server.
Example:
AD Server Name: SERVER1.DS.DOMAIN.COM
External Name Space: SERVER1.DOMAIN.COM
So they are trying to do a reverse lookup on the AD name space name,
instead of the external name space.
The only way I can see around this is to change the FQDN on the
outbound servers SMTP virutal server. This then works, but think it
will cause other issues for the internal sending/receive of messages as
this server works like a bridgehead as well to all of our sites.
What is the best way to deal with this issue? We just want it to put
the external name space in the header without messing up functionality
inside the network on these bridgeheads.
Thanks!
|
|
| Back to top |
|
 |
Transam388
Guest
|
Posted:
Tue Dec 27, 2005 5:58 pm Post subject:
RE: SMTP Server Name -- DNS |
|
|
Have you made sure to set your external SMTP as the default address instead
of your AD domain? The AD domain defaults as the SMTP address so when people
reply it would try to send to that domain instead of your externally
registered MX. Do not get rid of the AD domain though just set the other as
the defualt.
"dave313@gmail.com" wrote:
| Quote: | We are about to migrate to Exchange 2003 from Exchange 5.5 (late we
know :)
We are testing out the SMTP to the internet and things are working
well, execpt for those sites that are doing REVERSE lookups on the
server names.
We have setup reverse lookup for our outbound severs as or normal name
space, but it seems when the messages are delivered, they are looking
up the active directory domain name (which naturally isnt on the
outside of our network), instead of the public name space name for the
server.
Example:
AD Server Name: SERVER1.DS.DOMAIN.COM
External Name Space: SERVER1.DOMAIN.COM
So they are trying to do a reverse lookup on the AD name space name,
instead of the external name space.
The only way I can see around this is to change the FQDN on the
outbound servers SMTP virutal server. This then works, but think it
will cause other issues for the internal sending/receive of messages as
this server works like a bridgehead as well to all of our sites.
What is the best way to deal with this issue? We just want it to put
the external name space in the header without messing up functionality
inside the network on these bridgeheads.
Thanks!
|
|
|
| Back to top |
|
 |
dave313
Guest
|
Posted:
Tue Dec 27, 2005 5:58 pm Post subject:
RE: SMTP Server Name -- DNS |
|
|
Yes, we have our default address set to our external name. The problem is
really just wtih the way the header info is created for the message where it
puts the server name domain info for reverse lookups. It is the AD domain,
instead of the external domain.
Trying to figure out the best way to get the external domain to be the
default name for the server ,while not causing an issue working wtih the
internal domain.
"Transam388" wrote:
| Quote: | Have you made sure to set your external SMTP as the default address instead
of your AD domain? The AD domain defaults as the SMTP address so when people
reply it would try to send to that domain instead of your externally
registered MX. Do not get rid of the AD domain though just set the other as
the defualt.
"dave313@gmail.com" wrote:
We are about to migrate to Exchange 2003 from Exchange 5.5 (late we
know :)
We are testing out the SMTP to the internet and things are working
well, execpt for those sites that are doing REVERSE lookups on the
server names.
We have setup reverse lookup for our outbound severs as or normal name
space, but it seems when the messages are delivered, they are looking
up the active directory domain name (which naturally isnt on the
outside of our network), instead of the public name space name for the
server.
Example:
AD Server Name: SERVER1.DS.DOMAIN.COM
External Name Space: SERVER1.DOMAIN.COM
So they are trying to do a reverse lookup on the AD name space name,
instead of the external name space.
The only way I can see around this is to change the FQDN on the
outbound servers SMTP virutal server. This then works, but think it
will cause other issues for the internal sending/receive of messages as
this server works like a bridgehead as well to all of our sites.
What is the best way to deal with this issue? We just want it to put
the external name space in the header without messing up functionality
inside the network on these bridgeheads.
Thanks!
|
|
|
| Back to top |
|
 |
Andy David
Guest
|
Posted:
Tue Dec 27, 2005 5:58 pm Post subject:
Re: SMTP Server Name -- DNS |
|
|
On Tue, 27 Dec 2005 09:15:08 -0800, "dave313"
<dave313@discussions.microsoft.com> wrote:
| Quote: | Yes, we have our default address set to our external name. The problem is
really just wtih the way the header info is created for the message where it
puts the server name domain info for reverse lookups. It is the AD domain,
instead of the external domain.
Trying to figure out the best way to get the external domain to be the
default name for the server ,while not causing an issue working wtih the
internal domain.
|
Adding the domain to the FQDN dialog box on the virtual server
shouldnt cause any issues.
| Quote: |
"Transam388" wrote:
Have you made sure to set your external SMTP as the default address instead
of your AD domain? The AD domain defaults as the SMTP address so when people
reply it would try to send to that domain instead of your externally
registered MX. Do not get rid of the AD domain though just set the other as
the defualt.
"dave313@gmail.com" wrote:
We are about to migrate to Exchange 2003 from Exchange 5.5 (late we
know :)
We are testing out the SMTP to the internet and things are working
well, execpt for those sites that are doing REVERSE lookups on the
server names.
We have setup reverse lookup for our outbound severs as or normal name
space, but it seems when the messages are delivered, they are looking
up the active directory domain name (which naturally isnt on the
outside of our network), instead of the public name space name for the
server.
Example:
AD Server Name: SERVER1.DS.DOMAIN.COM
External Name Space: SERVER1.DOMAIN.COM
So they are trying to do a reverse lookup on the AD name space name,
instead of the external name space.
The only way I can see around this is to change the FQDN on the
outbound servers SMTP virutal server. This then works, but think it
will cause other issues for the internal sending/receive of messages as
this server works like a bridgehead as well to all of our sites.
What is the best way to deal with this issue? We just want it to put
the external name space in the header without messing up functionality
inside the network on these bridgeheads.
Thanks!
|
|
|
| Back to top |
|
 |
dave313
Guest
|
Posted:
Wed Dec 28, 2005 1:01 am Post subject:
Re: SMTP Server Name -- DNS |
|
|
In the testing it doesnt seem like it has...but really wanted to be sure
before we go into prodcution wtih this next week :)
If this truely doesn't this does fix my issue with the reverse lookups.
| Quote: | Adding the domain to the FQDN dialog box on the virtual server
shouldnt cause any issues.
|
|
|
| Back to top |
|
 |
Rich Matheisen [MVP]
Guest
|
Posted:
Wed Dec 28, 2005 1:58 am Post subject:
Re: SMTP Server Name -- DNS |
|
|
Andy David <adavid@pleasekeepinngcheesebucket.com> wrote:
| Quote: | On Tue, 27 Dec 2005 09:15:08 -0800, "dave313"
dave313@discussions.microsoft.com> wrote:
Yes, we have our default address set to our external name. The problem is
really just wtih the way the header info is created for the message where it
puts the server name domain info for reverse lookups. It is the AD domain,
instead of the external domain.
Trying to figure out the best way to get the external domain to be the
default name for the server ,while not causing an issue working wtih the
internal domain.
Adding the domain to the FQDN dialog box on the virtual server
shouldnt cause any issues.
|
It will if there's no "A" record for the name that your internal DNS
can resolve.
If your internal DNS can resolve the name to an IP address accessible
on your LAN things will work okay.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com |
|
| Back to top |
|
 |
Andy David
Guest
|
Posted:
Wed Dec 28, 2005 8:05 am Post subject:
Re: SMTP Server Name -- DNS |
|
|
On Tue, 27 Dec 2005 20:50:57 -0500, "Rich Matheisen [MVP]"
<richnews@rmcons.com.NOSPAM.COM> wrote:
| Quote: | Andy David <adavid@pleasekeepinngcheesebucket.com> wrote:
On Tue, 27 Dec 2005 09:15:08 -0800, "dave313"
dave313@discussions.microsoft.com> wrote:
Yes, we have our default address set to our external name. The problem is
really just wtih the way the header info is created for the message where it
puts the server name domain info for reverse lookups. It is the AD domain,
instead of the external domain.
Trying to figure out the best way to get the external domain to be the
default name for the server ,while not causing an issue working wtih the
internal domain.
Adding the domain to the FQDN dialog box on the virtual server
shouldnt cause any issues.
It will if there's no "A" record for the name that your internal DNS
can resolve.
|
Well, luckily there is a Check DNS button right there along
with the help dialog that tells you just that!
| Quote: | If your internal DNS can resolve the name to an IP address accessible
on your LAN things will work okay. |
|
|
| Back to top |
|
 |
Rich Matheisen [MVP]
Guest
|
Posted:
Thu Dec 29, 2005 8:23 am Post subject:
Re: SMTP Server Name -- DNS |
|
|
Andy David <adavid@pleasekeepinngcheesebucket.com> wrote:
[ snip ]
| Quote: | It will if there's no "A" record for the name that your internal DNS
can resolve.
Well, luckily there is a Check DNS button right there along
with the help dialog that tells you just that!
|
You actually READ that? :P
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com |
|
| Back to top |
|
 |
Andy David
Guest
|
Posted:
Thu Dec 29, 2005 8:29 am Post subject:
Re: SMTP Server Name -- DNS |
|
|
On Wed, 28 Dec 2005 21:23:27 -0500, "Rich Matheisen [MVP]"
<richnews@rmcons.com.NOSPAM.COM> wrote:
| Quote: | Andy David <adavid@pleasekeepinngcheesebucket.com> wrote:
[ snip ]
It will if there's no "A" record for the name that your internal DNS
can resolve.
Well, luckily there is a Check DNS button right there along
with the help dialog that tells you just that!
You actually READ that? :P
|
only when I can't sleep <g> |
|
| Back to top |
|
 |
dave313
Guest
|
Posted:
Thu Dec 29, 2005 5:58 pm Post subject:
Re: SMTP Server Name -- DNS |
|
|
Not an issue, we do have a A record that does resolve fine when checking wtih
the check DNS button.
Now, should I do anything with Masquerade domain? Set it to the true AD
domain?
| Quote: | Trying to figure out the best way to get the external domain to be the
default name for the server ,while not causing an issue working wtih the
internal domain.
Adding the domain to the FQDN dialog box on the virtual server
shouldnt cause any issues.
It will if there's no "A" record for the name that your internal DNS
can resolve.
If your internal DNS can resolve the name to an IP address accessible
on your LAN things will work okay.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com
|
|
|
| Back to top |
|
 |
Andy David - [MVP]
Guest
|
Posted:
Thu Dec 29, 2005 5:58 pm Post subject:
Re: SMTP Server Name -- DNS |
|
|
On Thu, 29 Dec 2005 05:56:04 -0800, "dave313"
<dave313@discussions.microsoft.com> wrote:
| Quote: | Not an issue, we do have a A record that does resolve fine when checking wtih
the check DNS button.
Now, should I do anything with Masquerade domain? Set it to the true AD
domain?
|
I generally leave that blank. Fill something in there if you need to,
but its used to enter an alternate domain for NDRs, so you probably do
not need it.
| Quote: |
Trying to figure out the best way to get the external domain to be the
default name for the server ,while not causing an issue working wtih the
internal domain.
Adding the domain to the FQDN dialog box on the virtual server
shouldnt cause any issues.
It will if there's no "A" record for the name that your internal DNS
can resolve.
If your internal DNS can resolve the name to an IP address accessible
on your LAN things will work okay.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com
|
|
|
| Back to top |
|
 |
|
|
|
|