Re: SBS 2003 R2 MX and A records



Thanks SuperGumby for the info on this. I will onsite Monday first thing to
hopefully unscrew this for her. I will followup on Monday afternoon with any
new info.
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:eUSlJ8%23KJHA.2164@xxxxxxxxxxxxxxxxxxxxxxx
it's OK, you can ignore it. No domain records exist so nothing is getting
queued anywhere (except on the originating servers).

Now's about the time I'd be assuming control of the DNS records for the
domain by any means possible. The domain exists in DNS and as Lanwench has
pointed out (through whois) the Sponsoring Registrar is Domain People Inc
with the responsible name servers being ns.siteprotect.com and
ns2.siteprotect.com. If Domain People cannot get it up _NOW_ they lose my
business.
.

This agrees with the current DNS inspection in that:
a)
Query: stetsonbaptistchurch.org. Query type: Any record
Recursive query: Yes Authoritative answer: No
Query time: 297 ms. Server name: ns2.siteprotect.com
The name server "ns2.siteprotect.com" refused to answer a query
(note you get same if you hit ns.siteprotect.com or ns2.siteprotect.com
directly)

b)
Registry Whois
Domain Name: siteprotect.com
Status: clientTransferProhibited
Registrar: DOMAINPEOPLE, INC.
Whois Server: whois.domainpeople.com
Referral URL: http://www.domainpeople.com

and c)
Registry Whois
Domain Name: hostway.com
Status: clientTransferProhibited
Registrar: DOMAINPEOPLE, INC.
Whois Server: whois.domainpeople.com
Referral URL: http://www.domainpeople.com

Though there are 'rules' about the current status of domain ownership I
find that 'proof of ownership' (call, ask, follow up with fax, company
letterhead, reqest for change) has allowed me to circumvent the associated
delays in transfer.

"Frank" <ffarero@xxxxxxxxxx> wrote in message
news:48f103da$0$13079$9a6e19ea@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi SuperGumby,

I am afraid the IT Lady just called the old hosting company (hostway.com)
and cancelled the service without doing anything else. When you say
"dequeue" what is it I have to do?
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:%237hxBG8KJHA.456@xxxxxxxxxxxxxxxxxxxxxxx
and...

You first need to look at what the current records are. It is _most
likely_ that the new hosting company has 'subsumed' your MX and any mail
destined for the domain is currently held on their servers. You need to
dequeue the existing mail before making any changes.

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23Cbvj07KJHA.1156@xxxxxxxxxxxxxxxxxxxxxxx
Frank <ffarero@xxxxxxxxxx> wrote:
Hi all,

SBS 2003 R2/single nic/ Exchange using SMTP / static IP from ISP

A new client just called and she stated that they are moving to a new
webhosting company so she cancelled their long time hosting company
and now cannot get mail or use RWW. She stated that the old hosting
company was hosting their MX and A records.

Why she suddenly cnxed the old hosting is beyond me.

Because she didn't know any better. One hopes that she will learn from
this.

Can I just call
up their ISP Brighthouse Networks to recreate the MX and A records?

She does not have access to the new hosting companies client website
control panel.

She needs to get access to the control panel - and needs to give you
the credentials. Then she needs to step back and not do anything
herself now that you're in the picture.

Thanks,

Frank

Did she change the nameservers for her domain to those of the new
webhost? If not, you need to do that with the registrar. I'd probably
go with a third party DNS host instead, because I like very granular
control of my DNS and the web host may not offer a fully featured
control panel - plus, I like to be able to move my webhosting wherever
I want without running the risk of mucking up my DNS. I personally
like www.dyndns.com.

Note that after the nameservers are changed, it will take some time for
this to be reflected everywhere. If you can preconfigure the new zone
with the appropriate A and MX records then do so, as it will make
things a lot faster once the nameservers are totally flipped.









.



Relevant Pages

  • NT DNS forward server can not find 163.coms MX record in the cache.
    ... I am using a NT DNS server in my internal network, the query to DNS server ... "Standard query MX 163.com", then HQ's DNS returned "Standard query response ...
    (microsoft.public.windows.server.dns)
  • Re: DNS
    ... If there is no name server at address $FOO, sending a DNS query will ... the resolver waits for a response ...
    (linux.redhat)
  • Re: DNS
    ... If there is no name server at address $FOO, sending a DNS query will ... the resolver waits for a response ...
    (linux.redhat)
  • Re: nslookup and internal server
    ... I create a domain on another hosting company B; ... DNS record to point to the server at B (the domain space is removed at ... Then you decided to move the website (not ...
    (microsoft.public.windows.server.networking)
  • Re: SBS 2003 R2 MX and A records
    ... Now's about the time I'd be assuming control of the DNS records for the ... Query: stetsonbaptistchurch.org. ... The name server "ns2.siteprotect.com" refused to answer a query ... I am afraid the IT Lady just called the old hosting company ...
    (microsoft.public.windows.server.sbs)

Loading