[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RAQ3 DNS Issues Primary & Secondary
- Subject: Re: [cobalt-users] RAQ3 DNS Issues Primary & Secondary
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Sat Apr 20 11:54:05 2002
- Organization: nobaloney.net
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Don't ask me how that bad email got posted... I'm not sure what I
pressed... here's the answer I intended, though...
Render-Vue wrote:
> a record domain.com with a the reverse look up checked
> a record www.domain.com
> a record mail.domain.com
> mx record domain.com --> 3rdparty.com preference 20
> mx record www.domain.com ---> 3rdparty.com preference 20
Looks good except you don't really need an mx record for
www.domain.com... no one in the real world ever sends email to
username@xxxxxxxxxxxxxx; only RaQs <wry grin>.
> The customer has their own server as they run a database off it so
> basically mail goes to 3rd party then onto their server.
> The problem we had was if people on one of the main ISP's networks sent
> email to them it came back as relaying denied yet on other networks it
> didn't. Now we had the ISP come back to us saying that the mail was getting
> rejected because they didn't recognise our secondary nameserver....
Nope.
All your nameserver is doing is telling the originating email server to
send mail addressed to user@xxxxxxxxxx to send the email to
3rdparty.com. And it's doing that by sending an IP address back to the
originating email server. The originating email server sends the email
to 3rdparty.com's IP# without any information at all about your
nameserver. That ISP has NO clue.
> now this
> is where I'm leading to.
>
> Remember took over the server with our own VNS already in place.
>
> Now I'm totally confused at the way the previous hosts have set this up as
> they changed the Server name from ns.theirname to ns.ourdomainname prior to
> taking over...
However it may very well be that your secondary nameserver isn't
properly registered. Since yo're not using your real domain name, no
one here can help you.
What are your real domain name, the real domain names of all the servers
shown in your examples, and the real names of your nameservers.
Without real information, we CANNOT help you. That's why you haven't
gotten any good answers. We can't help you if you hide the facts.
Hiding the facts is useless. All the information you're hiding must be
readily available and world-readable on the Internet. If it's not, NO
ONE CAN FIND THE SERVERS.
SO PLEASE STOP BEING SO PROTECTIVE IF YOU WANT US TO HELP YOU. Yes, I'm
shouting <wry grin>.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net
P. O. Box 52672, Riverside, CA 92517
voice: (909) 778-9980 * fax: (702) 548-9484