Re: General DNS config questions

True, I totally forgot about that. Only A-Z, 0-9 and - are allowed as characters in DNS... Sorry about that.

"Max C" <maxc246@xxxxxxxxx> wrote in message news:1180631943.797957.16440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for that very detailed information. Because of it, I now haev
a new piece of information that may or may not be important. When I
tried to add the MX record of @ pointing to NSSCO_SPAM, GoDaddy gave
me an obscure error message. It's wasn't at all descriptive. I tried
several things, finally thinking that it would only allow an IP
address for the MX record (because it states "Goes To - IP Address" in
the brief instructions.

After much fiddling, I finally figured out that it was the "_" in the
host name that GoDaddy didn't like. So, I've renamed my host
NSSCO_Spam to NSSCO-Spam. I'm now in the process of resetting my DNS
records. I'll keep you posted.

Mark.

On May 30, 6:38 pm, "Michael Dragone" <no.e-mail=less_spam> wrote:
"Max C" <maxc...@xxxxxxxxx> wrote in message

news:1180555591.925723.186130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

> Just to be 100% clear, when I set up the A and MX records for
> NSSCO_Spam, should I direct them both towww.xxx.yyy.37? I was under
> the impression that the MX record worked better if it was mapped to a
> host name rather than an IP.

No, no - you're right, it should be a hostname. You still set up the MX
record to point to nssco_spam.nssco.com and then set up an A record for
nssco_spam pointing to your .37 IP address.

> After a couple of days, you're saying you'd get rid of the "mail" A
> Record? If so, then that means you'd just adjust the "@" MX record to
> point to the NSSCO_Spam A Record?

Right now you'll add an A record for nssco_spam and change your MX record to
go to nssco_spam. When you're done, your zone will look like this:

A records
@ www.xxx.yyy.36(Web server)
mail www.xxx.yyy.37(spam filter)
www www.xxx.yyy.36(Web server)
nssco_spam www.xxx.yyy.37(spam filter)

MX records
Priority Host Goes To
0 @ nssco_spam

After a full day (or two to be safe - the default TTL for your zone is 1
day), you can remove the "mail" A record. By doing this you ensure that
anyone on the Internet that has cached "mail.nssco.com" as your MX will
still be able to resolve the hostname "mail" and send you messages while
anyone who has NOT cached the MX record will get your shiny new nssco_spam
hostname from an NX query.

If you're really paranoid you can keep the MX record for mail and set it to
a higher priority (10 would be good) for the same amount of time before you
delete it.

> I'm just trying to be thorough. I don't want to screw this up.

I don't blame you. Better to be safe.

.

Relevant Pages

  • Re: hostnames and interfaces
    ... > interface) and routers (multiple interfaces) can one define multiple ... > host names and IP addresses (strickly speaking that is what dns etc sees?) ... this can be a problem with a multi-homed host: ... Any machine will have a hostname -- that is the name which gets ...
    (freebsd-questions)
  • Re: can access IPs but not by hostname
    ... I know you said nslookup shows DNS is fine but, can you you ping a host name ... Using any browser by hostname fails with server can't be found. ...
    (microsoft.public.windows.server.general)
  • Re: exim HELO=fully qualified host name?
    ... > Basically correct. ... > You can test the system's idea of your host name either by running the ... (since one can't generally resolve the loopback address via DNS). ... suppose its less expensive than a DNS query, but specifying a hostname ...
    (Debian-User)
  • Re: General DNS config questions
    ... Thanks for that very detailed information. ... host name that GoDaddy didn't like. ... No, no - you're right, it should be a hostname. ... Better to be safe. ...
    (microsoft.public.windows.server.dns)
  • Re: hosts seems to not be used by the resolver
    ... Then look at tools like SSH that do reverse DNS lookups ... to verify that the host claiming to be "sshclient.whatever.com" and which is ... hostname so you can tell where someone was connecting from. ...
    (comp.os.linux.setup)