DNS woes..

Re: DNS woes..

From:

Date:

Time:

What if I have 40 domains and each one has a mail.thisdomain.com pointing to
the same IP address. How would they add the reverse name PTR to that IP?

For instance..

mmconsulting.com -> 67.92.79.20
mail.mmconsulting.com -> 67.92.79.4

mmcdata.com ->67.92.79.22
mail.mmcdata.com -> 67.92.79.4

Thanks in advance..

Mark

----- Original Message -----
From: "Global Homes Webmaster" <webmaster@globalhomes.com>
To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
Sent: Thursday, August 01, 2002 6:32 PM
Subject: Re: DNS woes..

> On 08/01/02 at 18:02, Mark Moloughney wrote:
>
> > This stuff is a real pain..
> >
> > If I have...
> >
> > mmconsulting.com -> 67.92.79.20
> > mail.mmconsulting.com -> 67.92.79.4
> > www.mmconsulting.com -> mmconsulting.com
> > ftp.mmconsultng.com -> mmconsulting.com
> >
> > Do I have to have the T1 provider set up PTRs for each of these?
>
> You only want one PTR for each IP address. So if the actual records for
the
> above look something like:
>
> mmconsulting.com. A 67.92.79.20
> mail.mmconsulting.com. A 67.92.79.4
> www.mmconsulting.com. CNAME mmconsulting.com.
> ftp.mmconsulting.com. CNAME mmconsulting.com.
>
> You would want two PTRs in the reverse zone (79.92.67.in-addr.arpa.) that
> look like:
>
> 4.79.92.67.in-addr.arpa. PTR mail.mmconsulting.com.
> 20.79.92.67.in-addr.arpa. PTR mmconsulting.com.
>
> The PTR for your mail server should resolve to whatever host name the mail
> server knows itself as (i.e., the name it introduces itself to other
> servers as). That's not absolutely required, but it will greatly reduce
the
> number of problems you might have with mail delivery.
>
> > DNS Expert is saying that it still can't find PTRs for the mail one..
> >
> > Whats up with that?
>
> The reverse zone for your Class C (79.92.67.in-addr.arpa.) is delegated to
> ns1.algx.net and ns2.algx.net. The in-addr.arpa. root servers say:
>
> % dig @arrowroot.arin.net. 79.92.67.in-addr.arpa.
>
> ;; AUTHORITY SECTION:
> 92.67.in-addr.arpa. 1D IN NS NS1.ALGX.NET.
> 92.67.in-addr.arpa. 1D IN NS NS2.ALGX.NET.
>
> ns1.algx.net says:
>
> % dig @ns1.algx.net. 79.92.67.in-addr.arpa.
>
> ; <<>> DiG 8.3 <<>> @ns1.algx.net. 79.92.67.in-addr.arpa.
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL:
0
> ;; QUERY SECTION:
> ;; 79.92.67.in-addr.arpa, type = A, class = IN
>
> ;; AUTHORITY SECTION:
> 79.92.67.in-addr.arpa. 1D IN SOA ns1.algx.net.
> hostmaster.algx.net. (
> 2002080165 ; serial
> 5h13m20s ; refresh
> 1H ; retry
> 5w6d16h ; expiry
> 1D ) ; minimum
>
> The existence of an SOA record, implies that there is actually a
> 79.92.67.in-addr.arpa. zone on ns1.algx.net. However, neither ns1.algx.net
> nor ns2.algx.net return PTRs for either of the above two IP addresses. I'd
> guess that your ISP (algx.net?) either hasn't finished setting up the zone
> yet, or they've got their thumbs firmly implanted where the sun don't
> shine.
>
> --
> Christopher Bort | cbort@globalhomes.com
> Webmaster, Global Homes | webmaster@globalhomes.com
> <http://www.globalhomes.com/>

Sales:
888/4-DPOINT

Support:
858/452-3696