PTR change tickets going to bit bucket?

[roamer1]

I got a server set up on Sunday...I noticed that the PTR for the server's IP didn't match the name of the server (the PTR appears to be that of the previous customer that had my IP.) Being familiar with how DNS server reloads are handled at other ISPs I'm familiar with, I figured I'd wait 48 hours.

Come Wednesday, I noticed the PTR still hadn't been updated, so I submitted a PTR change ticket through MySB...and didn't get a confirmation email, and the ticket never showed up in MySB. As of now the PTR is still wrong (which is causing email sent from the server to some picky domains to bounce since forward and reverse DNS don't match); given that the ticket seems to have just disappeared (never got email confirmation, never showed up in MySB, no other contact at all) I submitted a ticket *again* through MySB and once again got no confirmation email and the second ticket didn't show up in MySB either. :( At this point I'm assuming something's wrong with the ticket tool and the tickets are just vanishing before anyone ever sees them. Help!

-SC

[knightfoo]

PTR Requests do not generate a ticket or a confirmation e-mail. They are automatically submitted into our approval system, where someone reviews the requests and approves them. Sometimes the approval system can get a little backed up with all of the requests we get. They are processed in the order they are received, and they will be configured if everything is approved.

-knightfoo

[roamer1]

Originally posted by knightfoo
PTR Requests do not generate a ticket or a confirmation e-mail. They are automatically submitted into our approval system, where someone reviews the requests and approves them.
Makes sense...but the response from the ticket tool is a bit misleading. ;)

BTW: my PTR is now correct...looks like it got updated this morning. :)

-SC

[Zimm]

I'm a little confused. I've gone over multiple posts about PTR and always saw that I have to contact serverbeach through the support ticket requesting the PTR for a domain to be added.

After submitting a ticket and not getting a reply for two weeks ... I'm beginning to wonder ...

If my server itself is acting as the DNS for my domains, then I must have to add the PTR through whm and serverbeach doesn't need to get involved?

I don't mean to sound stupid, cuz I'm not :P Just confused. This is the first time running my own DNS server and as I said, I've read that serverbeach does the PTR records in previous posts.

[knightfoo]

Even if you are doing DNS for your domains, your server does not have the authority to set PTR records. All of the reverse zones are controlled by the ServerBeach nameservers.

All of the PTR requests that were pending have been approved. I could not find any tickets on your account, unless you have another account with us that I can't find. :) The PTR requests do not generate tickets, they go directly to our approval system.

-knightfoo

[Zimm]

Weird...

Well, I just submitted another one. A few mins ago, and got this once I clicked submit >

Your request has been submitted. Once it is enters our ticketing system you will recieve an email confirmation.
Continue

I'm sure I'm submitting them right ... I think ...

Login to myserverbeach
Request Support
Service Category: DNS
Service Sub Category: Reverse DNS/PTR Change

FQDN: <name>
IP: <ip>

Click submit :o

Maybe somethings the matter with myserverbeach account :confused: hmmm

[QT]

Originally posted by Zimm

I'm sure I'm submitting them right ... I think ...

Login to myserverbeach
Request Support
Service Category: DNS
Service Sub Category: Reverse DNS/PTR Change

FQDN: <name>
IP: <ip>

Click submit :o

Maybe somethings the matter with myserverbeach account :confused: hmmm

Looks right to me. Any updates (did they get your requests approved or are you still waiting)?

[Zimm]

no :( and now I have even more problems than before...ug

I submitted another ticket, this time through a different category that contained a 'PTR Request' subject. This time I did get a response from a 'Carl' and he said he fixed it.

He also proved it by pasting this:

"I put in a PTR record mapping 69.44.60.86 to tio.falcovprojects.com and
it is working:
$ host 69.44.60.86 ns1.geodns.net
Using domain server:
Name: ns1.geodns.net
Address: 66.139.72.14#53
Aliases:

86.60.44.69.in-addr.arpa domain name pointer tio.falcovprojects.com.
$

It will take 24-48 hours for this to propagate through the internet."

Either it still needs to propagate or something is messed up still :(
The time stamp on the ticket Carl sent was 2003-11-16 16:00:02-06

dnsreport.com is still giving me an error message though when I search for 'falcovprojects.com'

>> FAIL Reverse DNS entries for MX records ERROR: One or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
86.60.44.69.in-addr.arpa [No reverse DNS entry (rcode: 2 ancount: 0)]

Ho hum. I'll give it another night. Maybe propagation hasn't completed yet. Now the server is becomming UNresponsive every once and a while, but I ***think*** that might be software. Going to do some more investigation before I start submitting tickets about that though. :)