From: Chuck Campbell <campbell@accelinc.com>
To: Jens Knoell <jens@surefoot.com>
Cc: campbell@accelinc.com, linux-admin@vger.kernel.org
Subject: Re: DNS question
Date: Tue, 10 May 2005 10:23:02 -0500 [thread overview]
Message-ID: <20050510152302.GB24684@helium.inexs.com> (raw)
In-Reply-To: <200505100914.50299.jens@surefoot.com>
On Tue, May 10, 2005 at 09:14:50AM -0600, Jens Knoell wrote:
> Hi Chuck,
>
> On Tuesday 10 May 2005 09:01, Chuck Campbell <CC> wrote:
> > I've managed to completely confuse myself.
> >
> > I have a domain registered at a registrar and hosted at a provider.
> >
> > The provider has given me primary and secondary DNS names and ip addresses.
> >
> > I have entered those at the registrar's site. All whois queries work and
> > email is configured and working properly. I can find the web site from
> > anyone's browser.
> >
> > I now have a new company which has built commercial web pages for me, and I
> > need to make them active. This company says I need to change my DNS
> > addresses with my registrar to make this work. Is this correct? They will
> > then take over hosting the domain (become my NEW provider)?
> >
> > They do NOT do any email, so if I make the DNS server changes at my
> > registrar, will my email break?
> >
> > If not, then I'm not sure I understand how any of this works.
> >
> > I thought that my provider (ISP) puts up A and MX DNS records which allow
> > resolution of my web pages and my email addresses. If I switch to a new
> > provider that claims to not do email, who will make my email work?
>
> That provider is probably giving you a load of BS. I've seen providers who
> actually "need" the DNS resolvers on their servers, but in each case it's
> just a matter of total utter BS on their side. The only thing you need to do
> is point the www entry to the providers webserver.
Who (in my current situation) needs to point the www entry? I assume you mean
my current provider needs to change something to point web resolution to
a different address? What (so I can speak intelligently with them) needs to be
changed?
> Alternatively if you'd rather play along and transfer the domains nameservice
> to them, you can still add an MX entry pointing elsewhere if they don't
> provide email services.
I can't add an MX for email, the (new) provider would have to do that,
correct?
Are there some tools which let me see what A and MX records exist now, and
where they actually are living?
thanks,
-chuck
--
ACCEL Services, Inc.| Specialists in Gravity, Magnetics | (713)993-0671 ph.
2401 Fountain View | and Integrated Interpretation | (713)993-0608 fax
Suite 320 | Since 1992 | (713)306-5794 cell
Houston, TX, 77057 | Chuck Campbell | campbell@accelinc.com
| President & Senior Geoscientist |
"Integration means more than having all the maps at the same scale!"
next prev parent reply other threads:[~2005-05-10 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 15:01 DNS question Chuck Campbell
2005-05-10 15:14 ` Jens Knoell
2005-05-10 15:23 ` Chuck Campbell [this message]
2005-05-10 15:33 ` Jens Knoell
2005-05-10 15:37 ` Jens Knoell
2005-05-11 1:31 ` David Ziggy Lubowa
2005-05-10 15:20 ` Nick Mitchell
2005-05-10 15:26 ` Chuck Campbell
2005-05-10 15:39 ` Nick Mitchell
2005-05-10 15:24 ` Richard Nairn
2005-05-11 7:25 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050510152302.GB24684@helium.inexs.com \
--to=campbell@accelinc.com \
--cc=jens@surefoot.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).