Prev: leaf certificate
Next: Remove Remote Desktop Wallpaper in RWW Session on SBS 2008
From: Andrew M. Saucci, Jr. on 21 Mar 2010 22:15
That's your mistake right there. NEVER let the web design people
control your MX. They are almost invariably clueless and an unnecessary
obstacle. Get control of the DNS and point an A record for www.whatever.com
back to the web site and let the web design people stick to web development.
I have had innumerable problems with web design people allowing domain names
to expire, losing passwords, changing the MX back to their web mail,
disappearing when needed the most, and so on and so forth. They will gripe
and complain about the change in control, but generally, e-mail is more
important than the web site, and if the web site is down for a few days, the
client will be less concerned than if the e-mail is down a few days. I can't
have something so important in the control of clueless, unavailable parties
who don't know anything about networking or any other way than "point the
DNS to us."

"lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message
news:7BF92773-4A75-47E6-9B6C-9FCB26C63A3D(a)microsoft.com...

> The DNS is controlled by the web design agency people.


From: Andrew M. Saucci, Jr. on 21 Mar 2010 22:20
As an aside, I can usually verify a change in less than an hour--
sometimes within minutes-- by checking against the authoritative name
server, which is all I really care about. The "propagation" thing is true,
but the web people will just prolong the agony after they've messed it up by
hiding behind "propagation" as an excuse. If it looks wrong, I would not
wait three days to make sure it's fixed while a client has no e-mail. If a
change is purported to have been made and does not show up on the
authoritative name servers within an hour, I would assume that an error has
been made and insist that it be fixed immediately.

"Leythos" <spam999free(a)rrohio.com> wrote in message
news:MPG.260da012f25150498a1da(a)us.news.astraweb.com...
> In article <9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com>, lyje1
> @discussions.microsoft.com says...
>> I have made sure port forwarding is setup on the router, I can telnet
>> port
>> 25 to the server and I can send emails out. When I run a check on a MX
>> checker website for the domain it is showing no MX records whereas before
>> the
>> changes it was pointing correctly to mail.mydomain.com?
>>
>
> It can take up to 72 hours to see the changes.
>
>
>
> --
> You can't trust your best friends, your five senses, only the little
> voice inside you that most civilians don't even hear -- Listen to that.
> Trust yourself.
> spam999free(a)rrohio.com (remove 999 for proper email address)


From: Russ SBITS.Biz [SBS-MVP] on 21 Mar 2010 23:24
Andrew
I'm glad someone said it
I didn't want to be the one who did LOL
:)
Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Small Business Server/Computer Support - www.SBITS.Biz
Question or Second Opinion - www.PersonalITConsultant.com
BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com
Twitter http://www.twitter.com/SBITSdotBiz

"Andrew M. Saucci, Jr." <spam-only(a)2000computer.local> wrote in message
news:OSxDJWWyKHA.2012(a)TK2MSFTNGP04.phx.gbl...
> That's your mistake right there. NEVER let the web design people
> control your MX. They are almost invariably clueless and an unnecessary
> obstacle. Get control of the DNS and point an A record for
> www.whatever.com back to the web site and let the web design people stick
> to web development. I have had innumerable problems with web design people
> allowing domain names to expire, losing passwords, changing the MX back to
> their web mail, disappearing when needed the most, and so on and so forth.
> They will gripe and complain about the change in control, but generally,
> e-mail is more important than the web site, and if the web site is down
> for a few days, the client will be less concerned than if the e-mail is
> down a few days. I can't have something so important in the control of
> clueless, unavailable parties who don't know anything about networking or
> any other way than "point the DNS to us."
>
> "lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message
> news:7BF92773-4A75-47E6-9B6C-9FCB26C63A3D(a)microsoft.com...
>
>> The DNS is controlled by the web design agency people.
>
>
From: Russ SBITS.Biz [SBS-MVP] on 21 Mar 2010 23:25
Godaddy 2hrs max my experience in the USA
Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Small Business Server/Computer Support - www.SBITS.Biz
Question or Second Opinion - www.PersonalITConsultant.com
BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com
Twitter http://www.twitter.com/SBITSdotBiz

"Andrew M. Saucci, Jr." <spam-only(a)2000computer.local> wrote in message
news:O2Z#yYWyKHA.5040(a)TK2MSFTNGP02.phx.gbl...
> As an aside, I can usually verify a change in less than an hour--
> sometimes within minutes-- by checking against the authoritative name
> server, which is all I really care about. The "propagation" thing is true,
> but the web people will just prolong the agony after they've messed it up
> by hiding behind "propagation" as an excuse. If it looks wrong, I would
> not wait three days to make sure it's fixed while a client has no e-mail.
> If a change is purported to have been made and does not show up on the
> authoritative name servers within an hour, I would assume that an error
> has been made and insist that it be fixed immediately.
>
> "Leythos" <spam999free(a)rrohio.com> wrote in message
> news:MPG.260da012f25150498a1da(a)us.news.astraweb.com...
>> In article <9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com>, lyje1
>> @discussions.microsoft.com says...
>>> I have made sure port forwarding is setup on the router, I can telnet
>>> port
>>> 25 to the server and I can send emails out. When I run a check on a MX
>>> checker website for the domain it is showing no MX records whereas
>>> before the
>>> changes it was pointing correctly to mail.mydomain.com?
>>>
>>
>> It can take up to 72 hours to see the changes.
>>
>>
>>
>> --
>> You can't trust your best friends, your five senses, only the little
>> voice inside you that most civilians don't even hear -- Listen to that.
>> Trust yourself.
>> spam999free(a)rrohio.com (remove 999 for proper email address)
>
>
From: SuperGumby [SBS MVP] on 22 Mar 2010 00:33
similar story here. I query the responsible servers, if the change is
evident there then 'caching name servers' is somone else's problem.

"Andrew M. Saucci, Jr." <spam-only(a)2000computer.local> wrote in message
news:O2Z%23yYWyKHA.5040(a)TK2MSFTNGP02.phx.gbl...
> As an aside, I can usually verify a change in less than an hour--
> sometimes within minutes-- by checking against the authoritative name
> server, which is all I really care about. The "propagation" thing is true,
> but the web people will just prolong the agony after they've messed it up
> by hiding behind "propagation" as an excuse. If it looks wrong, I would
> not wait three days to make sure it's fixed while a client has no e-mail.
> If a change is purported to have been made and does not show up on the
> authoritative name servers within an hour, I would assume that an error
> has been made and insist that it be fixed immediately.
>
> "Leythos" <spam999free(a)rrohio.com> wrote in message
> news:MPG.260da012f25150498a1da(a)us.news.astraweb.com...
>> In article <9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com>, lyje1
>> @discussions.microsoft.com says...
>>> I have made sure port forwarding is setup on the router, I can telnet
>>> port
>>> 25 to the server and I can send emails out. When I run a check on a MX
>>> checker website for the domain it is showing no MX records whereas
>>> before the
>>> changes it was pointing correctly to mail.mydomain.com?
>>>
>>
>> It can take up to 72 hours to see the changes.
>>
>>
>>
>> --
>> You can't trust your best friends, your five senses, only the little
>> voice inside you that most civilians don't even hear -- Listen to that.
>> Trust yourself.
>> spam999free(a)rrohio.com (remove 999 for proper email address)
>
>


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