Ping blocks when looking up reverse dns PTR/RR

Hi!
If someone could shed some light on this behaviour, it would really make my day!
When using ping -s to ping an ip address that doesn't have a PTR RR, ping will timeout until dns timeout.
This would be fine, except that when the replys do show, it's response times are off the roof:
PING 80.79.163.74: 56 data bytes
64 bytes from 80.79.163.74: icmp_seq=0. time=5.65 ms
64 bytes from 80.79.163.74: icmp_seq=1. time=1.38e+05 ms
64 bytes from 80.79.163.74: icmp_seq=2. time=1.37e+05 ms
64 bytes from 80.79.163.74: icmp_seq=3. time=1.36e+05 ms
64 bytes from 80.79.163.74: icmp_seq=4. time=1.35e+05 ms
64 bytes from 80.79.163.74: icmp_seq=5. time=1.34e+05 ms
64 bytes from 80.79.163.74: icmp_seq=6. time=1.33e+05 ms
64 bytes from 80.79.163.74: icmp_seq=7. time=1.32e+05 ms
64 bytes from 80.79.163.74: icmp_seq=8. time=1.31e+05 ms
64 bytes from 80.79.163.74: icmp_seq=9. time=1.30e+05 ms
64 bytes from 80.79.163.74: icmp_seq=10. time=1.29e+05 ms
64 bytes from 80.79.163.74: icmp_seq=139. time=236. ms
64 bytes from 80.79.163.74: icmp_seq=140. time=5.92 ms
however, snooping while ping is busy with dns shows that packages do get transmitted and recieved, ping without -s works fine, ping -sn also works fine.
I can reproduce this on 8,9 and 10 of solaris, so I assume this is expected behaviour, although I cannot find any information about this issue, do you know more?
br, Christofer.
Edited by: oholiks on Jun 30, 2008 1:03 AM
added ping example.

Try to debug this:
nslookup -debug hostname
user@server# nslookup -debug aaa.aaa.aaa.aaa vld-dc-1
Server: domain-controller-1
Address: xxx.xxx.xxx.xxx#yy
QUESTIONS:
aaa.aaa.aaa.aaa.in-addr.arpa, type = PTR, class = IN
ANSWERS:
AUTHORITY RECORDS:
-> aaa.aaa.aaa.in-addr.arpa
origin = domain-controller-1
mail addr = admin.ru
serial = 26
refresh = 900
retry = 600
expire = 86400
minimum = 900
ADDITIONAL RECORDS:
** server can't find aaa.aaa.aaa.aaa. in-addr.arpa: NXDOMAIN
The solutions:
1) add correct dns records to resolve host names
2) add IP in /etc/hosts

Similar Messages

Exchange 2010 and reverse DNS

Hi
I have two exchange 2010 servers: x.x.x.72 and x.x.x.73
I have a reverse DNS ptr record for both of these machines pointing back to mail.mydomain.com
My users are getting an error message when they try to send mail to a craigslist.com address.
The error I see in the log is:
mail.mydomain.com [x.x.x.73] Please setup matching DNS and rDNS records: http://www.craigslist.org/about/help/rdns_failure
I have an A record [mail.mydomain.com] pointing back to .72
BUT I don't have an A record pointing back to .73.
So, I'm wondering is that what I need to do, create another A record and point .73 back to mail.mydomain.com
I was concerned having two A records pointing back to the same mail.mydomain.com. I wasn't sure if that would cause any problems.
Or should I create a send connector on .72 and only allow mail to be sent out for craigslist.com?
As you can see, I'm unclear on the best way to solve this.
Any advice is welcome.
Thanks!
Mike

Hi ,
If you wanted to use the x.x.x.73 ip address to send emails to internet then you need to have the proper A record and PTR records .
Please have a look in to the below mentioned points .Based upon the provided description i thought you are having like below.
Host A record :
mail.mydomain.com 192.168.1.72
PTR record :
192.168.1.72 mail.mydomain.com
Then on the send connector configuration you need have the smarthost as 192.168.1.72 to send emails to internet otherwise your emails get failed if the remote host has done reverse dns check.check. Because on your side i thought you don't have the proper
A records and PTR records for x.x.x.73
In case if you would like to have two A records .Please have the settings like below :-
Host A record :
mail.mydomain.com 192.168.1.72
mail1.mydomain.com 192.168.1.73
PTR record :
192.168.1.72 mail.mydomain.com
192.168.1.73 mail1.mydomain.com
On the above configuration you can make use of the both the ip's on the smarthost in the send connector to send emails to internet.
Note : You can make use of MXTOOLBOX to check the A and ptr records for your domain.
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Exchange 2013 Reverse dns setup

I recently migrated from SBS to Standard Windows servers with exchange 2013 and I'm having a heck of a time fighting spam. Mailflow is working fine, and we setup spam fighter exchange module which is catching most of the spam. However, it is missing some
that are spoofing our domain name with addresses that do and don't exist. I've read that the best way to stop this is to setup spf filtering and to do this you should setup reverse dns ptr records so you don't get blacklisted. The directions are rather confusing.
They say to setup a ptr record with your mail server's ip address. Here are my questions...
Do I have to set this up on both my dns and my service providers dns?
I currently have a A record and a ptr record pointing to the internal ip address on my internal dns server with the actual server name, but no records pointing to remote.domain.com.
Do I need to create additional A and PTR records using the External IP and remote.domain.com?
Right now my mx record points to mail.domain.com, but all of our connectors use remote.domain.com. Should the mx be changed to remote.domain.com?
Thanks for any help.

I've read that the best way to stop this is to setup spf filtering and to do this you should setup
reverse dns ptr records so you don't get blacklisted
Some antispam products to a reverse lookup on your IP address to make sure it matches the entry in the forward lookup zone. It does this to check that your server
is not spoofing the server name.
This won't necessarily prevent getting blacklisted (especially if you are sending spam), but it is definitely recommended for your mail architecture.
Do I have to set this up on both my dns and my service providers dns?
You will need to set this up on your Service Provider's DNS, as they will
technically own the IP address, and lease it to you.
Best practice is to have reverse lookup zones for your internal subnets in your internal DNS as well.
But this is not so much a spam related thing, as just a good idea.
Right now my mx record points to mail.domain.com, but all of our connectors use remote.domain.com.
Should the mx be changed to remote.domain.com?
This depends what these are used for. As you have come from an SBS environment, I'm guessing that both
of these names resolve to the same public IP address. If this is the case, you can leave the MX records as they are. If this is not the case, let me know and we'll discuss it later.
Let's say that you have a server called
mbx.contoso.com internally with an IP of
192.168.0.1. Externally, this server is known as mail.contoso.com
and has an IP address of 123.123.123.123.
In this case, you would do two things:
On your internal DNS server(s), create a reverse lookup zone for
192.168.0.0 and create a PTR record for
mbx.contoso.com with the IP of 192.168.0.1. This may already be done from when you set up Active Directory initially
Contact your ISP, and ask them to setup a
PTR record for mail.contoso.com for the IP
123.123.123.123

Forward DNS does not match reverse dns

Hi ALl
I have a fixed IP address via BT.
When I type the IP address into MxToolbox or similar i get this warning:
BT-UK-AS BTnet UK Regional network
Reverse DNS (PTR) exists and claimes to be: mail.concept-plc.com
Forward DNS for mail.concept-plc.com is: xx.xxx.xxx.xx
Should I be worried about this and if so who do i contact to do anything about it! Concept PLC seem to be a real company.
Are we sharing a fixed IP address?
Thanks for any help.
Solved!
Go to Solution.

Try the BT Business forum at http://business.forums.bt.com/
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Block Reverse DNS failures or not?

Hey guys,
Philosphical question, which I honestly didn't think I'd have to ask...
Do you block messages from servers that fail reverse DNS lookup (eg no pointer record or non matching pointer record)?
We recently tightened things up, and put those in the blacklist, and I'm seeing more legit senders getting dropped than I expected.
Am I expecting too much?
Ken

You can enable these three checkbox in the sendergroup BLACKLIST:
-Connecting host PTR record does not exist in DNS.
-Connecting host PTR record lookup fails due to temporary DNS failure.
-Connecting host reverse DNS lookup (PTR) does not match the forward DNS lookup (A).
Be aware for the False positives.

Is there a way for my daughter or her friends to block their numbers from showing up on activities page. At first i could see them, as of yesterday i can no longer see the numbers in the activities page. But i do see that she has texted them when looking

Is there a way for my daughter or her friends to block their numbers from showing up on activities page. At first i could see them, as of yesterday i can no longer see the numbers in the activities page. But i do see that she has texted them when looking at her phone.

First of all, there is no need to put the entire text of your post into the title of your thread.
Next, does your daughter have an iPhone? Do her friends have iPhones? If the answer to both questions is "yes", then it is possible she is not texting them, but using iMessage to communicate with them. iMessages will not show up in the texting traffic on a line as they are not texts, but messages sent thru Apple's servers.
For all "texts" to show up in the texting activity of an iPhone, you must disable iMessage on the device. Any messages sent as iMessages(blue bubbles around the text) on an iPhone will not show up in any texting activity.

Why is the router sending reverse DNS queries ?

Hi all,
While doing a trace for a traceroute command, i realize that the router is actually doing a reverse DNS query for the ip that I am doing the traceroute.
Although this does not impact my traceroute, I can't help to wonder why the need to do the reverse DNS for ?
1   0.000000000   192.168.5.1   255.255.255.255   DNS   84   Standard query 0x2f3e PTR 2.5.168.192.in-addr.arpa
3   5.750328000   192.168.5.1   255.255.255.255   DNS   84   Standard query 0x2f3e PTR 2.5.168.192.in-addr.arpa
5   10.828742000   192.168.5.1   192.168.5.2   UDP   60   Source port: 49246 Destination port: 33435
6   10.859994000   192.168.5.2   192.168.5.1   ICMP   70   Destination unreachable (Port unreachable)
Regards,
Noob

Hi Jon,
Thanks. I hope you really dont mind me asking - to assist to take a look at these 2 related threads below (as i spend an entire day doing testing and researching but to no avail)... ;(
Hope you are able to shed some light ;(
https://supportforums.cisco.com/discussion/12492246/pinging-remote-broadcast-address-cant-understand-response
https://supportforums.cisco.com/discussion/12490926/ping-no-response-found-what-does-it-meant
Thank you

Warning - Reverse DNS does not match SMTP Banner

I have a installed in exchange server 2013 in the Home network. Everything looks fine. But Reserve DNS was not setup properly. Reverse DNS is not matching with my domain. "Reverse
DNS does not contain the hostname" when I checked in MXToolBox.com
I have configured FQDN on port 25 to mail.xxxxx.com. I don't know what else need to configure as Iam new to exchange.
Can some give me some steps to do this?
ItsMeSri SP 2013 Foundation

Reverse DNS (aka PTR record) is something set at your ISP level, not on your Exchange server. If you have a static IP from your provider you should be able to contact them (or log into the ISP's portal) to change the reverse DNS. If you have a dynamic IP
(meaning you didn't pay extra for a static) you will be unable to set your reverse DNS.
The implication's of not having a matching reverse DNS is that many email providers will not allow you to send them email (ex. aol.com, hotmail.com). I am actually in the same boat (on a dynamic IP) but I set up my Exchange to send all my email through a
spam filter service. If you send through a reputable spam filter you should have no issues sending to any email providers (even though reverse DNS checks will still fail).

Gateway set up DNS/PTR

Hi , I need to set up an Xserve as a gateway for our office LAN The Xserve connects to a locked ISP provided router on the WAN side (public IP) and on the LAN side to a switch and on to our clients.
I need to know exactly what my ISP needs to have set up in their DNS records, as I understand it they must have a "A" record and MX but my ISP Tech tells me that I need WWW * etc etc but when he puts all of these in my xserve picks up the incorrect FQDN.
I expect "server.mydomain.com" but I get "mydomain.com" which i assume will the cause problems with my local realm ?
Any help with the correct terms etc so I can explain to them what I require.
Many Thanx

Your phrasing of the question raises all kinds of red flags for me…
First off, you can have only one PTR record. If this server is running as a mail server for your domain then that PTR record should match whatever name you choose for your mail server/MX record (e.g. 'server.mydomain.com' is fine as long as your MX record points to 'server.mydomain.com' and your mail server is configured to identify itself as 'server.mydomain.com'.
If your ISP is also managing DNS for your domain then you should then have ONE 'A' record for your nominated hostname (e.g. server.mydomain.com with the associated IP address).
Any other hostnames that map to your site (either services such as web that are running on this machine, or services that are NATted at this server to an internal machine) should be setup as CNAME records to the above A record.
For example:
Forward DNS:
mydomain.com MX 10 server.mydomain.com.
server.mydomain.com A 123.45.67.89
www.mydomain.com CNAME server.mydomain.com.
foo.mydomain.com CNAME server.mydomain.com.
Reverse DNS:
89.67.45.123.in-addr.arpa PTR server.mydomain.com.
What worries me about this all, though, is that it sounds like you have a single server, and that server is publicly-facing.
If this server is also running services such as Open Directory (maintaining the list of user accounts), DNS (for your internal clients), file sharing, etc. then these services by default will all be publicly exposed and you will leak your internal domain data to the outside world. You will be targeted to dictionary and brute force attacks and you risk compromising your network as a result.
In other words I do not recommend running a single server for all services as well as a NAT gateway. It takes too much time and effort to secure the server. Do yourself a favor and get a $50 NAT router to act as your network edge device (connected to your ISP's router) and sleep easier at night.

Set up reverse DNS for virtual mail hosting

I need a bit of server configuation advice.
I have a static IP and two public domains on a Snow Leopard server connected using NAT behind a firewall - with the necessary port forwarding to ensure all works.
1. abc.com is my primary domain on the server - server.abc.com
2. I have xyz.com set up as a virtual domain and also as a virtual mail host
This setup has worked well for a long time but I have found that emails to [email protected] are going missing. If I check my mx records using one of the web based tools it show an error on the reverse dns for server.xyz.com showing a reverse DNS of server.abc.com.
So the question - is it possible to have secondary 'virtual' DNS record on the server so reverse DNS works for the virtual mail host xyz.com? If not how do I handle the reverse DNS problem which i think is causing some external mail server to reject mail due to the inconsistency on the reverse DNS lookup?
Many thanks for any suggestions

SMTP requires a DNS A record.
A DNS A record is also known as a machine record.
A DNS A record inherently means that forward DNS and reverse DNS will match.
The forward translation translates the host name to the IP address.
The reverse translation translates the IP address to host name.
When the full translation produces the same host name, that's an A record.
DNS CNAME records are aliases, and are used for virtual hosts.
CNAME records inherently do not match the reverse DNS translations.
To get your configuration to work, your server must have an A record.
That means forward and reverse DNS will match.
Any of the virtual hosts within your mail server then all use an MX pointing at the A record host.
If you have your DNS hosted somewhere other than your ISP, then you'll need your ISP to set up a DNS PTR.
The DNS PTR is the reverse translation; address to name.
If you have your own DNS services within your network (as would be typical with a privately-addressed NAT'd network), set that up as a virtual host within SMTP.
Here is some related reading on external (public) DNS, as related to SMTP servers and such.

OS X 10.4.11 Server - configured name and reverse DNS do not match / DNS

Hi all,
I have looked for similar posts but all seem to have different scenarios, hoping to get an answer from someone more experienced than myself before I do anything silly.
Help much appreciated!
Scenario:
We run a 10.4.11 OS X Server on an XServe, hosted at an ISP. ISP provides all DNS services, incl. the reversed DNS entry.
I am currently only running the following services (based on the display in ServerAdmin):
AFP
Firewall
iChat
Mail
QuickTimeStreaming
Web
All others (incl. DNS) are grayed out. (As ISP instructed us not to add a DNS service on our box, that's "normal" according to my experiences with dedicated /co-location server hosting).
We never used changeip after the initial setup, meaning the server's
Current Hostname = somename.local and
DNS Hostname = mail.ourdomainname.net
So in system.log I find this re-occuring entry:
Jul 8 11:41:22 somename servermgrd: servermgr_dns: configured name and reverse DNS name do not match (somename.local != mail.ourdomainname.net), various services may not function properly - use changeip to repair and/or correct DNS
Finally, my question:
As Mail and Web services etc. are currently running OK from what I can tell,
1) do I HAVE to change this at all?
2) Would it be much better / why?
3) Could I change this using the following command
(111.11.111.1 indicating the server's IP address)
changeip 111.11.111.1 111.11.111.1 somename.local mail.ourdomainname.net
4) without running a DNS server on the machine, i.e. DNS service is not required for this to work?
5) obviously I want to be able to use Server Admin after I issue this command...
6) can I fall back easily in case this would screw it up, or is there no risk whatsoever doing this in my case?
THANK YOU so much for any help!

Hi Jonas
If port 443 is already being used on the same box as KMS then it will complain and probably not start the service? I've seen this with LDAP port 636. This is when Kerio is installed on a server configured as an OD Master. Clearly the port can't be used by both servers.
It might be easier to change the port your sites are currently using to something else? Although don't do anything yet. Pose the question to Kerio Support and see what advice they offer.
Yes moving the mail to a local folder on the mail client will do it.
Is Kerio going on the same box? If its a different box (presumably different IP address?) Then what you can do is to port forward to the new server's IP address instead of disabling it. This way while you are bringing the new server on line users can still send mail right up until the time you give instructions on changing their inbound/outbound mail server details. Of course they won't be able to receive but if you time it right they may not even get an error message? Depends on what their schedules are.
If it was me I would choose IMAP every time. As the mail admin you have full control and a central location for easy backup. KMS has a built in archiving feature that makes this a simple process. This is an easier option than going round individual client machines and making sure mail held locally in POP accounts are backed up. Besides there is always someone who falls through the loop and I'm not taking into account drive failures. It makes good sense anyway as there is talk of legislation being introduced to make this a requirement for businesses who run their own mail servers. This is certainly true for certain parts of the US and what usually happens there is generally taken up in the UK and most parts of Europe.
Kerio's WebMail Client means users don't even have to have their own computer. Just as long as they have access to one that has access to the internet they can send/receive mail. No need for dedicated mail applications such as Apple Mail, Thunderbird, Entourage etc. How mail is uses remains consistent for all users.
Yes. I did this not so long ago with Leopard's built in Mail Server. I sent an e-mail defining a time when no inbound mail would be received. Disabled port forwarding for SMTP port 25 and approx 30 minutes after that another mail stating no outbound mail should be sent. Once everything was swopped over (we were changing from a G4 10.4 server to a G5 10.5 Server) port 25 was enabled, new server brought online and everyone was mailing again with no appreciable downtime.
These boxes were to have the same IP address hence the slightly different approach.
Does this help?
Tony

Reverse DNS does not match SMTP Banner

Hello,
We have a client with an SLS who is configured to send mail using the ISP as relay. With this situation, the server-side mail rules (vacation notices) are not working.
So, I need to configure the server to use DNS to send mail. The client has one public static IP, in the form of client.static.isp.gr. ISP refuses to change the PTR for a single IP, so when I check the server using mxtoolbox.com, I get +Reverse DNS does not match SMTP Banner+.
In MS Exchange, you can set the "Internet e-mail name" and change the default SMTP banner.
How can I change the SMTP banner in Postfix? (in order to put the ISPs PTR for the static IP).
Regards
Kostas

Kostas B. has been tussling with other issues ("ISP refuses to change the PTR for a single IP") and this is unrelated to the configuration of Mail itself, from what I can tell of it. He's really trying to do something that the ISP involved isn't supporting, and that's more of an administrative or ISP issue and less of a technical issue.
As for your question (and presuming your public-facing DNS forward and reverse translations are correct and your MX record is correct, details which are not yet in evidence), launch Server Admin and set your mail server host name in the mail configuration. Server Admin > select server > Mail > general > fill in your internet-facing host name. This name should matche your public DNS MX record, and your public forward and reverse DNS translations should (also) match.
And as a general rule, please don't thread-jack. That largely serves to confound and confuse the discussions.

DSL Down - Looks Like a DNS Issue

Hi Everyone,
My DSL service has been down for 36 hours now and while Verizon is looking into the issue, I'd like to see if this community has any ideas as to what's going on. Here's the story:
My Internet access went down at midnight two nights ago. I have two computers and both lost their connection, so I'm confident that it's not an issue with either computer. I have an Actiontec modem/wireless router from Verizon. I have rebooted the modem, which usually resolves any issues, but in this case it didn't help. When I do an ipconfig, the DNS Suffix shows as domain_not_set.invalid, which I don't believe I've ever seen before. I'm unable to ping any sites and nslookup reports DNS failures.
Verizon is sending me a new modem, but I tried using my old Westell modem from Verizon and I'm seeing the exact same issues, so I'm thinking it's not a modem issue.
Verizon has tested my line multiple times and says everything seems fine. The issue has now been escalated to their central office to see if there is an issue there.
Since Verizon hasn't been all that helpful to date, I'm wondering if anyone has had a similar issue and can point me in the right direction. If the central office doesn't see an issue, the next step is for a tech to come for a visit.
Thanks in advance.
Edit: I should also mention that while on the phone with Verizon I reset the modem, so it's back to the factory defaults.

Oh yes, it has nothing to do with you or me or any computer, I myself am experiencing the second outage in less than a week. Mine has been down AGAIN since sometime last night. I was told when I called on Monday that nearly everyone in my area code had no service, that was an equipment problem. I finally got a call on Tuesday, an automated message, saying that is had been resolved, and so it had. For less than 2 days. Now it's out again and I see nothing at all about it here on this website. I have waited all day to use my husband's wireless card so I could catch on my stuff and also come here to see if there were some answers, but of course there are none. Big surprise. To say that I am unhappy is the understatement of the month. This is unacceptable service and it is especially galling that nothing that I have seen is giving customers explanations for this latest outage. I would like to see someone from Verizon explain what is going on here in my part of Southern California about why we keep losing our DSL service.

Reverse DNS not working

Noticed today that reverse DNS is no longer working for our (10) VMs. It was yesterday and had been for several weeks.
I removed and re-added one of them. Waited for over an hour and still not resolving.
PS C:\Windows\system32> Get-AzureService "emvpodeast2"
ServiceName             : EMVPodEast2
Url                     : https://management.core.windows.net/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/services/hostedservices/EMVPodEast2
Label                   : EMVPodEast2
Description             : emvpodeast2 with Reverse DNS
Location                : East US
AffinityGroup           :
Status                  : Created
ExtendedProperties      : {[ResourceGroup, EMVPodEast2], [ResourceLocation, East US]}
DateModified            : 12/23/2014 10:32:34 AM
DateCreated             : 9/2/2014 7:44:55 PM
ReverseDnsFqdn          : fathersonholyghosttown.com.
WebWorkerRoleSizes      : {}
VirtualMachineRoleSizes : {}
OperationDescription    : Get-AzureService
OperationId             : xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
OperationStatus         : Succeeded
PTR Check:
http://mxtoolbox.com/SuperTool.aspx?action=ptr%3a191.238.18.70&run=toolpage

I'm having the exact same issue here.
There were no IP changes. Reverse DNS was working until it wasn't anymore. We noticed it on the 22nd December when about 400 e-mails were refused from our newsletter because there was no reverse DNS.
Tried reconfiguring like SIRob45 but to no avail.
PS C:\> Get-AzureService "assistimo"
ServiceName             : assistimo
Url                     :
https://management.core.windows.net/cac66cff-7d19-41a7-a012-e2197e145d36/services/hostedservi
                          ces/assistimo
Label                   : assistimo
Description             : S4 reverse DNS
Location                : North Europe
AffinityGroup           :
Status                  : Created
ExtendedProperties      : {[ResourceGroup, assistimo], [ResourceLocation, North Europe]}
DateModified            : 24/12/2014 17:33:26
DateCreated             : 14/11/2014 13:50:26
ReverseDnsFqdn          : s4.assistimo.pt.
WebWorkerRoleSizes      : {}
VirtualMachineRoleSizes : {}
OperationDescription    : Get-AzureService
OperationId             : 670e5f9b-206d-5b41-a3c7-f5acf5f89fcd
OperationStatus         : Succeeded
Results from
http://mxtoolbox.com/SuperTool.aspx?action=ptr%3a191.235.218.152&run=toolpage:
ptr:191.235.218.152
No ptr Records exist
History results:
Type
IP Address
Domain Name
TTL
PTR
191.235.218.152
assistimo.cloudapp.net
1 min
smtp diag
blacklist
port scan
subnet tool
Reported by PRD2.AZUREDNS-CLOUD.NET on 12/1/2014 at 11:15:54 AM (UTC -6),
just for you.  (History)  Transcript
Session Transcript:
MXTB-PWS3v2 468ms
  0  f.in-addr-servers.arpa  193.0.9.1  NON-AUTH  109 ms  Received 8 Referrals , rcode=NO_ERROR    NS tinnie.arin.net,NS ns-lacnic.nic.mx,NS ns3.afrinic.net,NS ns.lacnic.net,NS
sec1.authdns.ripe.net,NS sec3.apnic.net,NS a.arpa.dns.br,NS ns2.lacnic.net,
  1  tinnie.arin.net  199.212.0.53  NON-AUTH  31 ms  Received 5 Referrals , rcode=NO_ERROR    NS PRD1.AZUREDNS-CLOUD.NET,NS PRD5.AZUREDNS-CLOUD.NET,NS PRD3.AZUREDNS-CLOUD.NET,NS
PRD4.AZUREDNS-CLOUD.NET,NS PRD2.AZUREDNS-CLOUD.NET,
  2  PRD2.AZUREDNS-CLOUD.NET  65.55.117.43  AUTH  46 ms  Received 1 Answers , rcode=NO_ERROR    PTR assistimo.cloudapp.net,
We have no support contract and cannot submit a support request as suggested.
Thank you in advance.
Carlos R. Calado

Setting up reverse DNS

I've run my own DNS for some years under OS X Server, but in the past couple of months have had a real problem with mail from my domain to AOL and other domains bouncing since my reverse DNS was handled by AT&T, which returned one of those "consumer"-type adsl-whatever zone names instead of my zone name, neko.com. AT&T has now delegated reverse zone lookups to my server.
My IP block extends from 71.158.134.193 through 71.158.134.222. Neko.com is 71.158.134.213.
I've used Server Admin to set up the reverse zone file, which it created and named "134.158.71.in-addr.arpa." Reverse lookups, i.e. "dig -x 71.158.134.213" don't work; AT&T insists the reverse zone file should be called "192.134.158.71.in-addr.arpa".
Of course renaming the file doesn't work since that's not the file name in named.conf. But I don't see any way to specify an IP range or net mask in Server Admin; it's as though it can't handle anything less than a full class C domain.
Any hints?
G5 Quad Mac OS X (10.4.7)

The reverse zone file should be called:
/private/var/named/hosts/masters/134.158.71.in-addr.arpa-hosts
and inside that file you should have something like this:
@ 1D IN SOA dns.neko.com. hostmaster.neko.com. 2007071905 8H 2H 1W 2H
@ IN NS dns.neko.com.
@ IN NS ns1.neko.com.
213 IN PTR neko.com.
Explanation: "dns.neko.com" would be your primary dns server.
"ns1.neko.com" would be your secondary dns server.
"hostmaster.neko.com" would be your hostmaster email address ([email protected]).
NOTE: all domains end in period (ie, there is a '.' after every 'com') - that is not a typo!
NOTE: use a period for the 'at' sign in you hostmaster email address - do NOT use @ there - that is also not a typo!
some good resources:
http://www.menandmice.com/knowledgehub/dnsqa/49
http://www.menandmice.com/knowledgehub/dnsqa/56
The AT&T people are confused. You have to cut them some slack though, they're too busy playing with their new iPhones to know what they're talking about.

Ping blocks when looking up reverse dns PTR/RR

Similar Messages

Maybe you are looking for