Prev: leaf certificate
Next: Remove Remote Desktop Wallpaper in RWW Session on SBS 2008
From: Brian Cryer on 22 Mar 2010 05:26
"lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message
news:7BF92773-4A75-47E6-9B6C-9FCB26C63A3D(a)microsoft.com...
> Hi All,
>
> Thanks for the replies. If I type in: nslookup -type=mx mydomain.com, it
> doesn't bring up a mx record? The DNS is controlled by the web design
> agency
> people. They have deleted mail.mydomain.com and replaced it with
> remote.mydomain.com. Should they have removed the mx record for
> remote.mydomain.com, recreate the mx record for mail.mydomain.com,
> repointed
> the IP address to the server and create a new A record for 'remote' to the
> same IP address?

There is your problem. As others have already said: (i.) your web design
agency has broken it and (ii.) don't let them near your DNS settings.

Whether you have mail.mydomain.com or remote.mydomain.com, in itself doesn't
matter. What is important is that the lookup for your MX records returns a
valid IP address - the public IP address of your server.

Yes, they (or you if you can get control of DNS back from them) need to add
an MX record for your domain. Since mail.mydomain.com and
remote.mydomain.com are sub-domains they don't need to come into the
equation at all - although I can see the convenience in pointing (say)
mail.mydomain.com to your public IP address and then defining the MX record
for your domain by using mail.mydomain.com. Personally I wouldn't bother,
but I can see why others do it. As for "remote.mydomain.com" I'd guess that
is to support outlook web access, but that's only a guess. Its your MX
records which are missing and which need to be created.
--
Brian Cryer
www.cryer.co.uk/brian

First  |  Prev  | 
Pages: 1 2 3 4
Prev: leaf certificate
Next: Remove Remote Desktop Wallpaper in RWW Session on SBS 2008